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

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

1069.0. "ALLIN1/NOINIT in command procedure gives "Enter CMD:"" by COMICS::BARHAM (Norbert:) Fri Jul 17 1992 09:01

    ALL-IN-1 2.4 patched to K604
    
    My customer has written a command procedure to run ALL-IN-1 without 
    initialization and perform a few functions (within a DO script), thus:
    
    $! TEST.COM
    $ ALLIN1/NOINIT
    DO TEST
    EXIT
                                       
    His problem is that when he does @TEST.COM he gets the "Enter CMD:" prompt
    instead of having the TEST.SCP (which is in the same directory) executed.
    
    It works fine for me. My script (and his) contains one line 
    
    oa$txl_list wpslps,do
    
    When I then type @test.com, it calls test.scp correctly and displays
    the code for the DO script WPSLPS. It then gives a message as expected :-
    
    BARHAM finished using ALL-IN-1 at 13-Jul-1992 15:51
    
    
    My customer says that when he does <command test to run the command 
    procedure interactively it works, but when he does @test from DCL it
    gives the "Enter CMD:" prompt.
    
    I haven't checked for any oaini.scp yet but they would apply in both
    cases (?).
    
    sys$input is defined to be sys$command.
    
    Any ideas why he gets the prompt running the procedure from DCL ?
    
    Thanks
    
    Clive
T.RTitleUserPersonal
Name
DateLines
1069.1Terminal type? Batch?IOSG::PYEGraham - ALL-IN-1 Sorcerer&#039;s ApprenticeFri Jul 17 1992 09:278
    Could it be something to do with what his terminal is? Or to be more
    exact, what VMS, and hence we, think it is. If the image can't identify
    the terminal type, or thinks it's a LA100 or similar, then you'll get
    the command prompt.
    
    Is your test interactive rather than batch?
    
    Graham
1069.2correctCOMICS::BARHAMNorbert:Fri Jul 17 1992 10:5320
    Thanks Graham, we're getting somewhere now.
    
    VMS is 5.4 on a VT320 and we're not running in batch. The setup has 
    VT300 mode, 7 bit controls, VT320 id and VT320 v1.2 and when we 
    <get oa$terminal it says 'VT300 series'. 
    However, when we run @sys$manager:a1wpsplus_login, it says 
    
    Unrecognized terminal type, please see your system manager.
    
    In this procedure it does
    
    TERM_TYPE := 'f$getdvi("tt:","devtype")
    
    This returns a value of "1" which is obviously the problem ! But why, I
    don't know yet. I'll look into it.
    
    Thanks
    
    Clive