Conference noted::hackers_v1

    VMS V5 ships with a native mode TECO.  You no longer need VAX/RSX.

    We just installed IFT2 of VMS V5.0 - no TECO. Where is it?
    
    Kevin

    $ EDIT/TECO
    
    invokes TECO32.EXE.  Looks like TECO32 does most of the work in
    SYS$SHARE:TECOSHR.EXE.  Does this mean we have callable TECO now?
    
    -piper

    I may go back to TECO, but I am still curios on how to change the
    record attributes.

    To get the correct record attributes, use
    
    $ convert document.mem document.doc/fdl=sys$input
    record
    	carriage_control carriage return
    ^Z
    $ 
    
    #ken	:-)}

RE: .-1
>   	carriage_control carriage return
                                ^^^
    probably a typo, but the above should be:
    
    	carriage_control carriage_return
                                ^^^
RE: all
    and if you want to bypass TPU and TECO altogether, use a 3-step
    convert
    
    $ convert document.mem document.tmp/fdl=sys$input
    record
    format undefined
    ^Z
    $ convert document.tmp document.tmp/fdl=sys$input
    record
    format stream
    carriage_control carriage_return
    ^Z
    $ convert document.tmp document.txt/fdl=sys$input
    record
    format variable
    ^Z
    
    actually, you could stop after step-2, but step-3 is for perfectionists

To return to an earlier topic:  Yes, there's a fully-native TECO that will
ship with V5; yes, its main image is TECO32, not TECO, which is why MCR TECO
will fail (but MCR TECO32 will succeed); yes, it is fully callable, supporting
the standard callable editor interface (so CALLABLE_TECO will work as your
MAIL editor, for example), plus a bunch of other calls to provide a pretty
complete interface between TECO and other progarmming languages; and, yes,
Digital has it now - it runs on V4, and has done so for quite some time.

All give a big hand to Rick Murphy, who did the port.

For more information, see the TECO notesfile on DSSDEV.

							-- Jerry

    Thanks, Jerry....
    To use it, any of EDIT/TECO or TECO:==$TECO32 or DEFINE TECO TECO32
    will do it for you. For VMS V4 systems, the kit is at UFP::TECO32$KIT:
    	-Rick

    RE: .6
    
    	I gripe. 
    
    	I ran the procedure, that used only CONVERT, and it worked with
    	VMS V4.7.   
    
    	So I copied it onto my V5 system, and it didn't work - all
    	the records were concatenated together, then divied up into
    	512 byte ones.
    
    	Hmmm...

    ... but don't let me imply that it was a VMSV5 problem.
    
    Basically, the reason that the file got re-organized seems to be
    that there were no CRLF's in the first place. 
    
    The TPU-followed by-CONVERT method seems to be working on all cases.

  >    ... but don't let me imply that it was a VMSV5 problem.
    
    It works for me on FT5.0 (X5.0-3N2).
    If it didn't, it *would* be a VMS (convert) problem.

    I tried what was recommended in .6 and found what looks like a bug. 

    After the <FF> below is the data file I use.  After the second <FF>
    is the result I get from a VMS 4.6 system.   The last line of the file
    is getting messed up.

David

    Here is the command file I use:

$ convert 'P1 $cvtrec.tmp/fdl=sys$input
record
format undefined
$EOD
$ convert $cvtrec.tmp $cvtrec.tmp/fdl=sys$input
record
format stream
carriage_control carriage_return
$EOD
$ convert $cvtrec.tmp 'P1/fdl=sys$input
record
format variable
$eod
$ delete $cvtrec.tmp;*







         ___ ___ ___ ___ ___ ___ ___

        |   |   |   |   |   |   |   | 

        | d | i | g | i | t | a | l |   I N T E R O F F I C E  M E M O

        |___|___|___|___|___|___|___|





        also  checks to see that both machines get xyzzy abcdef faults

        on the same pages (order independent).



             To enable xyzzy abcdef fault checking, the user must  add

        the  /TNV qualifier to GENERATE, PRINT, and VERIFY, as well as

        /VIRTUAL_MACHINE=ON to GENERATE and PRINT.




         ___ ___ ___ ___ ___ ___ ___
        |   |   |   |   |   |   |   | 
        | d | i | g | i | t | a | l |   I N T E R O F F I C E  M E M O
        |___|___|___|___|___|___|___|


        also  checks to see that both machines get xyzzy abcdef faults
        on the same pages (order independent).

             To enable xyzzy abcdef fault checking, the user must  add
        the  /TNV qualifier to GENERATE, PRINT, and VERIFY, as well as
        /VIRTUAL_MACHINE=ON to GENERATE and PRI
NT.