Conference hydra::amiga_v1

    Ray,
    It is possible that the problem is that there is a space
    following the "Switcher" keyword, before the first "(".  Check that first.
    Second, I think this would actually cause a syntax error, but does 'RAM:'
    need to be enclosed in quotes?  I can't recall what the syntax is for
    the Switcher command.
    
    Clark

    
    
    My statement is Switcher(FSDV,RAM:) and according to VT instructions
    this is the correct syntax.  NewTek tried using the statement with
    Remote.rexx and it seemed to work, I'll give it a try, but don't see
    how it could make a difference.  Every problem I've encountered to this
    point with the VT had a logical solution to, this one isn't making much
    sence. 
    
    Thanks,
    ~Ray
    

Could it be that Rexx is interpreting the string RAM:? If so, the ':' should
cause Rexx to complain about the Syntax (n.b.: I don't have an ARexx
handy, but Cowlishaw doesn't list ':' as allowable in symbols).

Without seeing how the command is being issued, I can't say for sure
whether the RAM: is being interpreted by ARexx. But if it is, the ':' should
cause Rexx to complain about the Syntax (n.b.: I don't have an ARexx
handy, but Cowlishaw doesn't list ':' as allowable in symbols).

	<mike

    Hi.  I have (perhaps related) a problem with an ARexx macro, and I
    figured I'd try to consolidate notes and put a reply here.
    
    I'm accessing HANDSHAKE, the Vt220 emulator.  In the ARexx document,
    there are listed commands and functions.  I'm able to access the
    functions just fine, an example:
    
    address HANDSHAKE
    
    return_boolean = hs_string('Print this string to serial port')
    
    However, I can NOT access the commands.  In the document, one is listed
    as:  HS_TIMEOUT seconds    <specifies the timeout for GETSTR>
    
    So, I:
    
    address HANDSHAKE
    
    HS_TIMEOUT 30
    
    I get:  Host environment not found (even though the functions work)
    
    I tried address HANDSHAKE 'HS_TIMEOUT 30'
    
    I get:  same thing.
    
    Am I missing some important part of ARexx syntax for external commands
    (which I couldn't find in the reference manual), or is Handshake
    screwing up?
    
    thanks,
    Mike

    RE: .5 
    
    Uh-oh, I don't know what you mean by REPLYS.  I'd better read my ARexx
    manual real careful to find out what you mean.
    
    Sorry for my inexperience,
    Mike

    RE: .3
    
    What doesn't make sence is that I can execute Remote.rexx and input
    "FSDV RAM:" and it enables RAM for framestore.  So, it seems ARexx
    is interpreting the ":" when it's stored in one of the "Arg" varibles.
    I inserted "Switcher(FSDV,RAM:)" in between "say 'READY'" and "do
    forever" in the Remote program... no luck.  Any ARexx command that 
    requires DF0: DH0: or RAM: doesn't work for me. I've tried every 
    combination including leaving the ":" out of the statement.  
    
    It's probably a very simple oversight somewhere... but I can't figure 
    that somewhere out! 
    
    ~Ray

    
    I'm thinking that REPLY was meant for the gentleman who wrote the base
    note, but assuming it was for me...
    
    I see it's part of the included function library, and you specify a
    packet (4-byte address) and a whole number return code.  Unfortunately,
    that's all the manual says about it, and from their description it
    sounds like a low level command, where I'd need to know the packet
    (how?) and the code I'm supposed to return (in Handshake_ARexx.doc?).
    
    Can someone please elaborate?  Thanks in advance,
    
    Mike

Did you try putting the device name in quotes instead of leaving it out?

I don't have VT, but from the description it seems like VT wants the
:. Since that's not valid in any part of a Rexx expression except a string
or label, you'll need to quote it. I.e.:

Switcher(FSDV, 'RAM:')

Though if FSDV isn't a a variable, I'd recommend:

'Switcher(FSDV, RAM:)'

to make the entire thing a string.

	<mike

    
    Mike your right and .3 also.  I just talked to another individual at 
    NewTek and he said that RAM: had to single be quoted, then ARexx would 
    see it as a string var, and that also explains why it worked in Remote.rexx
    since it plugged it into a Arg var.
    
    Thanks for the feedback.
    
    ~Ray