|
Whether you decide to rewrite a ton of programs or write some new programs is up to you. The Virtual Terminal APIs do allow one program to emulate a workstation user and so you could use your existing *DSPF based programs and have them "fed" by a program. These are not easy APIs to use as they require a very good knowledge of 5250 data stream, but it can be done. Using the Virtual Terminal APIs does not stop your COBOL program from appearing to be an interactive job, it simply eliminates the need for a physical display device and user to provide the input (which I believe is what you want). The APIs can be found in the Information Center under Programming/APIs/APIs by category/Virtual Terminal Bruce "Bullerman,Arlene" <abullerman@xxxxxxxx To: "COBOL Programming on the iSeries/AS400" <cobol400-l@xxxxxxxxxxxx> o.com> cc: Sent by: Subject: RE: Local Data Area question cobol400-l-bounces@x idrange.com 06/24/2003 02:49 PM Please respond to COBOL Programming on the iSeries/AS400 Hmmmmm......then I guess I'd better keep trying to win the lottery and get started on rewriting a ton of programs. -----Original Message----- From: Winchester Terry [mailto:terry.winchester@xxxxxxxxxxxxxxx] Sent: Tuesday, June 24, 2003 2:44 PM To: 'COBOL Programming on the iSeries/AS400' Subject: RE: Local Data Area question > -----Original Message----- > From: Bullerman,Arlene [mailto:abullerman@xxxxxxxxxxxxx] > Sent: Tuesday, June 24, 2003 3:23 PM > To: COBOL Programming on the iSeries/AS400 > Subject: RE: Local Data Area question > > > My co-worker and I just had this same conversation. So, you > haven't had any luck getting around the 'screen file' issue? > Is it possible to 'attach' the screen file to a dummy device > and then let it run? Nope. The way I understand things is that you must either acquire a physical device -or- already be connected to a workstation. You might be able to compile the program with some sort of "dummy device" and use an OVRDSPF but it won't execute. I think it may have to do with the system code thats linked into the program object - which is probably using the DSM API's to connect to a physical device. This is all speculation since I'm not part of the Cobol compiler team ;-) Again, if a solution to the interactive tax was this *simple* then IBM and all those other vendors would be in deep kimshee ;-) If you find a solution to this you'd be a hero in the AS/400 world and could write your own ticket :) Terry _______________________________________________ This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/cobol400-l or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-l. _______________________________________________ This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list To post a message email: COBOL400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/cobol400-l or email: COBOL400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/cobol400-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.