RE: BYSYNC Problems

[Tim McCarthy <TimM@xxxxxxxxxxxxxxxxxx>]

The difference between 2780 and 3780 bisync comes down basically to the
record separator you use - X'1F' v/s x'1E'. Changing the controller to
call a new number should work. The first thing to verify is that the
modems do indeed sync up - a lot of banks and insurance companies use
the old BELL 201/208 modems which won't work with your V32/35 modem. Do
you see any data sent at all? Use TRCICF or STRCMNTRC to verify. If you
do you may want to check your blocking size. Start off with the block
size set to the record size (slows throughput but good for a check). 

> -----Original Message-----
> From: Mike Cunningham [SMTP:MCUNNING@pct.edu]
> Sent: Wednesday, July 14, 1999 7:37 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      BYSYNC Problems
> 
> Our bank is upgrading some software for credit card deposits  to
> Connect Mailbox at their end.  I currently do a BYSYNC file transfer
> using a home grown RPG application.  The homegrown application works
> fine but just changing the controller to call a new number does not
> work.  The modems connect and appear happy but the RPG application
> gets stuck waiting for permission to send the first record (a $$ADD
> statement).  They say they are BYSYNC 3780 are their end.  Does anyone
> know how to file transfer an 80 byte file to a 3780 device ?
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---