Re: PROGRAMS in Pathway

On Apr 1, 2:07 pm, Keith Dick <kd...@xxxxxxx> wrote:
What you say surprises me a little.  My experience with Pathway was that everyone used PROGRAMs to test their Screen Cobol programs.  But the situations I saw were all with users whose applicatons used only 6530 terminals, where nothing extra had to be done beyond setting up the PROGRAM.  Maybe the use of PROGRAMs is much less among programmers who develop Screen COBOL for 3270 terminals.

Keith, there are a several reasons for that.
1) In a development environment, most developers have multiple 6530
TACL windows open and it's very easy to do a RUN PROGRAM in one window
while debugging the Screen Cobol requester or the server in another
window.
2) If an organization has a need for Screen Cobol program to run on
both 6530 and 3270 terminals, it is usually done by using a compile
toggle around the respective OBJECT-COMPUTER clauses. The rest of the
program is usually identical. Since the code is identical, most
testing is done via 6530 sessions since those are more commonly
available.
3) In a production environment, users generally don't have access to
TACL, so RUN PROGRAM is seldom used in a production environment
regardless of whether it is a 3270 or 6530.
4) One major difference between the 3270 and a 6530 is that the 3270
is a block mode only device. Unlike the 6530 it does not have a
native conversational mode. ETN3270 simulates conversational mode by
painting a block mode screen with an 80 character unprotected row.
When a function key is hit, that row is read back and returned to the
conversational program that posted the writeread. ETN3270 maintains
an internal scroll buffer so the most recent 23 lines are displayed
each time the "conversational" screen is repainted. So it is somewhat
pedantic to start a TACL on a 3270 just to do a RUN PROGRAM to start a
block mode SCOBOL program, although it is indeed possible.
.

Relevant Pages

  • Re: PROGRAMS in Pathway
    ... TACL windows open and it's very easy to do a RUN PROGRAM in one window ... ETN3270 simulates conversational mode by ... painting a block mode screen with an 80 character unprotected row. ...
    (comp.sys.tandem)
  • Re: porting 32-bit to 64-bit on Xeon
    ... IDE to build 64-bit applications while you maintain the same code base ... To set the 64-bit build environment variables, ... Build Environment Window", point to "Set Windows XP 64 Build ... change the folder to the \Microsoft Visual ...
    (microsoft.public.vc.mfc)
  • Re: do while help please.....
    ... environment where `window' is not defined. ... And without define all alert, setTimeout etc as a properties of Global ... is related to concrete host environment - browser host environment. ...
    (comp.lang.javascript)
  • RE: VS6 and intel C++ 8.0 - how to compile for WIN64?
    ... Because the native 64-bit IDE is still under ... #toc: back to the ... To set the 64-bit build environment variables, ... Build Environment Window", point to "Set Windows XP 64 Build ...
    (microsoft.public.vstudio.general)
  • Re: [OT] crontab & gnome-schedule do not run bash script
    ... Among them are the "terminal lines" going to your keyboard and display. ... terminals, these ports came to be known as "tty lines". ... When you login, and/or start a terminal window, you are given ownership ... If you login to a graphical environment many things about the window ...
    (comp.unix.shell)