DAL and VAX: Async Connection Issue

I am evaluating Data Access Language (DAL, formerly known as "CL/1"). I set up an asynchronous connection (through a modem) to a VAX with Red Ryder with these settings:

1200 baud
No parity
8 data bits
1 stop bits
XON/XOFF

I connect to another VAX using DECnet with a "c MIS001". This is the VAX with the DAL server running. Leaving the terminal session open and using the DAL test application, I invoke this host connection script direct1200:

direct1200:async:com1:1200:Noparity:8databits:1stopbits:Bothxonxoff:128:Nomodem

This returns a "connection failed", error 10628(0) asynch() with no message.

I tried using the async1 host:

async1:async:com1:1200:Noparity:8databits:1stopbits:BXonxoff:128:Modem:Tone::se
cs:attempts

This returns a "Connection to host async failed", error 10643(0) async() with no message.

Then it returns a "connection failed", error 10628(0) async() with no message.

I think this is because of the round-about connection to the host, but it seems if I already made the connection, the DAL tester should piggyback on the connection. I verified that the AppleTalk connection works and can access data this way. Therefore, it does not seem to be a server-based problem.

1) What script should I use for this type of connection?

2) How easy would it be to write a host script, so I don't have make the connection through Red Ryder?
We talked with Network Innovations, and they stated that their asynchronous protocols work only with VAX systems directly connected to the asynchronous link (in this case, the modem). In other words, they do not support logging on to one host, connecting to a second host via DECnet, and running the DAL server from that second host. They are aware of this issue and are looking at ways to resolve it in the future, but there is no workaround at the present time.
Published Date: Feb 18, 2012