Selecting The Connection Directory In Aspect

[KeithFrench]

I am designing a script in Procomm Plus V4.8 which will need use a different connection directory than the default. In Aspect, how can I select the Connection Directory file name to use for the duration of the script. I would have thought that it could be done with a set command, but cannot see the one to use. Any ideas?

 

[RLHarris]

Use the "dialload" command to load a new connection directory.

Dialload (path and name of directory)

For some weird reason, this is a command rather than a set/fetch statement.
Robert Harris
Communications Advantage

http://www.communicationsadvantage.com

 

[gbk]

I'm having trouble with the dial command, dialing a connection directory entry. I'm using the exact same name, exact case: dial DATA "Entryname"

I even added a findfirst command to verify it's finding the connection directory exists, and it is.

Then I added a dialload to make sure I was accessing the correct directory, but I can't determine if this sucessful.

I'm running version 4.8.

Appreciate any help. Thanks.

 

[knob]

What happens when you try to dial the Entryname connection? Do you have your dialload command before or after the dial DATA "Entryname" command? You can determine if the dialload command was successful or not by checking for success or failure immediately after the command. The structure would look something like this:

dialload "dirname.dir"
if success
usermsg "success"
else
usermsg "failure"
endif

 

[gbk]

Okay, got it to load the connection directory now, but it won't connect after I dial. I can connect manually. When it dials out, will the "dial" screen display like it does manually? This is my first dialout script.

I'm using the dial DATA "entryname". After that I have a message to the screen termmsg "Attempting to dial". Do I need to include a pause statement while it connects?

Not sure what I'm missing.

Thanks.

 

[knob]

After your dial command, place this block of code:

while $DIALING
yield
endwhile

This will pause your script while Procomm is in the process of connecting to the other system. After that, you could check the value of $CARRIER to make sure the connection was made or not, and then your script could handle each situation appropriately (continue with the script or display an error message and exit).

 

[gbk]

Thanks, I've got the connection working now.

Is there a way to display the responses from the host that I'm calling to the screen - like in manual mode? I tried using
set capture recordmode RAW
but that didn't make any difference. I'd actually like to "see" the responses from the host if I can .

Also, if there a way to verify a transmit command actually sent the file? I didn't see anything in the help file.

Thanks.

 

[gbk]

In answer to my own question regarding the determing the status of the sendfile command (not transmit), I placed a the while loop to get the status of $XFERSTATUS.

Will test tommorrow - can't connect right now.

 

[knob]

Unfortunately, there's not a way to get the results codes and such from the modem unless you are in modem command mode. This is due to Procomm using TAPI to communicate with the modem and I believe TAPI is the limiting factor here.