Conference csc32::consolemanager

822.0. "Console Extract crashed with RMS-W-RTB - IBM console" by 60600::BROOKS () Fri Jun 16 1995 07:50

    
    Hi,
    
    	I have come across a problem with PCM Console Daemon and how it writes 
    the logfile data. The Console Connect/monitor will format the data
    correctly , but the Console Daemon writes all the data on one line
    without any <CR><LF>.
    
    	So when you try to EXTRACT the data using PCM, it will crash with a 
    -RMS-W-RTB, 4851500 byte record too large for user's buffer.
    
    	Now the system is a IBM console connected to a Black Box protocol
    converter to a DECSERVER, setup correctly at 8 bits noparity , 1 stop
    bit. This console was migrated from VCS and I'm told that VCS wrote the
    logfile correctly.
    
    	I have dumped out the logfile with the DUMP/REC and got the same
    message.
    
    %DUMP-E-READERR, error reading CONSOLE$ROOT:[LOG]HDS.LOG;1
    -RMS-W-RTB, 4851500 byte record too large for user's buffer
    
    	A dump/block will give you access to the data inside;
    
    Dump of file CONSOLE$ROOT:[LOG]HDS.LOG;1 on 14-JUN-1995 16:04:06.29
    File ID (629,1,0)   End of file block 9480 / Allocated 9480
    
    Virtual block number 154 (0000009A), 512 (0200) bytes
    
     2D2D2D2D 2D2D2D2D 2D2D2D2D 2D2D2D2D ---------------- 000000
     2D2D2D2D 2D2D2D2D 2D2D2D2D 2D2D2D2D ---------------- 000010
     2D2D2D2D 2D2D2D2D 2D2D2D2D 2D2D2D2D ---------------- 000020
     345B1B20 48313B34 5B1B202D 2D2D2D2D ----- .[4;1H .[4 000030
     1B48333B 32325B1B 206D305B 1B48343B ;4H.[0m .[22;3H. 000040
     30332E32 31202D20 20202048 313B335B [3;1H    - 12.30 000050
     20313032 34344E20 46204620 2031352E .51  F F N44201  000060
     44484F44 20545345 55514552 20535446 FTS REQUEST DOHD 000070
     54532046 4F44204F 54205053 5043464F OFCPSP TO DOF ST 000080
     31352E30 332E3231 202D2044 45545241 ARTED - 12.30.51 000090
     3B345B1B 2048313B 345B1B20 20202020      .[4;1H .[4; 0000A0
     41205353 414C4348 383B345B 1B204834 4H .[4;8HCLASS A 0000B0
     313B355B 1B204830 383B345B 1B20202E .  .[4;80H .[5;1 0000C0
     2D2D2D2D 2D2D2030 30206D31 5B1B2048 H .[1m 00 ------ 0000D0
     2D2D2D2D 2D2D2D2D 2D2D2D2D 2D2D2D2D ---------------- 0000E0
     2D2D2D2D 2D2D2D2D 2D2D2D2D 2D2D2D2D ----------------
    
    As you can see there are not any CR/LF characters (0A,0D), but just
    screen formating commands.
    
    I have read a similar note entry about a SUN 7 bit systems having a
    similar problem. The customer said that the protocol converter setting
    have not been changed since it was working on VCS
    
    I'm lost as to where to go from here ? help....
    
    Regards,
    Niguel Brooks
    CSC Sydney
    
    
    

Can you send me a copy of the log times and event files for this 
system so I can try to reproduce this as I thought I had a fix in
for this sort of huge line!!!.

Cheers Simon....

    Simon,
    
    	Thanks for taking the time in looking into the call, I have
    requested a copy of the files from the customer and will make them
    available asap.
    
    Cheers..
    Nigel

    Hi Simon,
    
    	I now have the files from the customer and they are located on our
    machine via the name RIPPER or 60576::
    
    Thanks,
    Nigel 
    
    
    Ripper_> dir ripper""::DUMPFILES:[BROOKS.Q61631]/sec/size=all
    
    Directory RIPPER""::DUMPFILES:[BROOKS.Q61631]
    
    CONSOLE.BCK;1           5229/5232          [340,15]        (RWED,RWED,RE,R)
    HDS.EVENTS;1               2/4             [340,15]        (RWED,RWED,RE,R)
    HDS.LOG;5               4634/4636          [340,15]        (RWED,RWED,RE,R)
    HDS.TIMES;1                2/4             [340,15]        (RWED,RWED,RE,R)
    
    Total of 4 files, 9867/9876 blocks.
    

Niguel,
        I have run the logs you sent me against V1.6 PCM extract and
I do not get a crash. I put some extra line length checks in the
V1.6 extract to cater for cases where the output does not have many
line feeds ( due to other controls for screen handling). The OpenVMS
kits for this are in the process of being submitted so they will be
available to yuor customer. Look for the announcement in this notes
conference. The kit which will be put up will be what is submitted to 
SSB for shippeing to customers so it will be supported.

Cheers Simon....

    Simon,
    	
    	Thanks for verifying the fix  was in V1.6 and I'll get my hands on
    a early copy of V1.6 so I could do the checks locally before posting out 
    my problem.
    
    Cheers,
    Niguel