I do not remember, if I ever knew, the SWIFT network backbone. All I ever had to deal with was writing the communications to send packets of information to custodian banks. About the time I started working on the project, SWIFT was just getting started as, I believe, a rebadged version of something else. The name of which is totally lost in the recesses of my mind.
My system was a combination of OS/2 and Windows (3.1 no less). Because it was trade (read mutual fund trade) based we could process over 65,000 transactions a day. Of course the information packets were small, sometime less than 256 bytes. It sounds like your system was needed for much larger file transfers which poses a different set of problems... Not to start another stroll down the OS/2 lane, I remember someone asking me why I did not write everything for Windows. I tried to explain to him that OS/2 would wrap the PID number and still keep on running. I tried it with Windows and after about 1,000 transactions it would crash because of memory leaks or any host of other reasons. Ah... those were the days....... :) -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ed Gould Sent: Friday, January 11, 2008 1:27 AM To: [email protected] Subject: Re: File Transfer conundrum I don't recall too much about SWIFT. Just that it existed that is about all. Was it connected with TANDEM (et al) ? In anycase we had only two customers that didn't do SNA and I think one of them was using RSCS (bisync I believe) and some RJE emulator oh yes JES3 I had almost forgot. Bisync was pretty good (but not as good as SNA, IMO). There were 3rd party options of course but that entailed a healthy invest in software. The company I worked for was the cheapest of the cheap so any 50K (or more) investment would have been looked on with extreme displeasure. We did look at one or two but there were issue that we just could not live with. One was that software (I am sorry I can't remember the vendor name) was a little (read a lot) OS dependent. I had talked to a user about incompatibilities between the vendors software level. Trying to get everyone synced up was a nightmare according to him (especially when it came to 200+) . We wanted to make this as transparent as possible and we exceeded far beyond my original estimates. The IBM utility we used was sold (it *NEVER abended* because of program logic and we typically used it 10K times a day (or more) the number of times a day gets a little murky as we had two data centers and we transmitted to our DR site many times more files that 10K. I can't say enough about a solid product like this was. Once installed it hasn't been touched in 20 years over many OS releases and zero problems, show me any equal numbers from any OEM and we can talk. I am no longer with that company but I was pretty proud as to what I implemented in such a short amount of time. Ed <http://e-mail-servers.com/1c7cfcab4f28fab40bc238c9aee06e71worker.jpg> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
