|
Jerry, I couldn't find even a starting point. Must have off-loaded the code to tape... I looked at Shannon O'Donnell's example code, and I didn't understand much of it (probably because I don't know anything about CPI-C). And when folks start talking ack/nak's and all that, I'm less than clueless. What I recall of the process is a BSC file, opened in the RPG as a WORKSTN. Needed the right keywords (IIRC, TURNAROUND,etc.) and needed the read/write loops JUST SO... Take me 3 years to recreate that kind of thing...;-) It might compile, but wouldn't run... Give me a clue and I'll run with it for a while... But I won't recall the fundamentals, so won't be able to answer any questions about why the code doesn't work... Don't have sufficient interest, myself, to actually test and debug the thing... So I can only run with it, to a point... jt | -----Original Message----- | From: midrange-l-admin@midrange.com | [mailto:midrange-l-admin@midrange.com]On Behalf Of Jerry Sprout | Sent: Thursday, November 29, 2001 6:57 AM | To: midrange-l@midrange.com | Subject: Re: Command to read from a (communication) LINE | | | well, all the hard stuff is done. I thought you might just clean it up. | You know, close. | ----- Original Message ----- | From: "jt" <jt@ee.net> | To: <midrange-l@midrange.com> | Sent: Wednesday, November 28, 2001 7:35 PM | Subject: RE: Command to read from a (communication) LINE | | | > "moose", | > | > Glad to see you finally joined the M-L list. However, point of | etiquette | > here: I haven't looked at BSC in what? 15 years, so I might not be able | to | > answer any questions that come up... So hopefully someone with more | recent | > experience can offer here... | > | > jt | > | > | -----Original Message----- | > | From: midrange-l-admin@midrange.com | > | [mailto:midrange-l-admin@midrange.com]On Behalf Of Jerry Sprout | > | Sent: Wednesday, November 28, 2001 7:00 PM | > | To: midrange-l@midrange.com | > | Subject: Re: Command to read from a (communication) LINE | > | | > | | > | I have a set of CL commands that do bisync communications. | The program | is | > | an MI program I wrote back in the 38 days. You cannot use | this program | if | > | your AS/400 is at level 40 or higher because it crosses the | domains. I | > | started an attempt to rewrite this program in RPGILE. Once I | got ready | to | > | test it, the project was benched 'cause the guy that wanted to go to | level | > | 40 got fired. It is really a pretty simple thing. The most | complicated | > | part is making a connection. That is where I was testing. Doing | > | autodialing. Let me know how you are connected (dialup, | direct, leased | > | line). Maybe I can get the program to work for you. (Actually, | > | I'll get JT | > | to do it.) Hopefully you won't have too much need for other bisync | tasks. | > | > _______________________________________________ | > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing | list | > To post a message email: MIDRANGE-L@midrange.com | > To subscribe, unsubscribe, or change list options, | > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l | > or email: MIDRANGE-L-request@midrange.com | > Before posting, please take a moment to review the archives | > at http://archive.midrange.com/midrange-l. | | | _________________________________________________________ | Do You Yahoo!? | Get your free @yahoo.com address at http://mail.yahoo.com | | _______________________________________________ | This is the Midrange Systems Technical Discussion (MIDRANGE-L) | mailing list | To post a message email: MIDRANGE-L@midrange.com | To subscribe, unsubscribe, or change list options, | visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l | or email: MIDRANGE-L-request@midrange.com | Before posting, please take a moment to review the archives | at http://archive.midrange.com/midrange-l. |
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.