Ticket #94 ( Pending IE )

Short Description built-in screen definition for blank screen
Entered By: PeteL When: 1998-07-17 04:07:48 Build: 1.03.19c
Categories Type: Suggestion   Department: Product   Category: SurferScript
Nice-to-have - a built-in variable called something like UNFORMATTED_BLANK that could be used in a screen definition, ie.
this would allow a very simple definition for the universally applicable blank screen, instead of having to define 24 AND SCREENs with 80 blanks. Not really sure if there is much need for a FORMATTED_BLANK, but if not, could drop the "UNFORMATTED".
Append By: WindSurfer  When: 1998-07-17 12:56:02  New Status: Accepted
Comment This isn't hard to do, will try to get it in soon--how about:



Append By: PeteL  When: 1998-07-21 06:04:51  New Status: Closed
Comment works fine - thanks
Append By: PeteL  When: 1998-07-21 06:36:23  New Status: Pending IE
Comment i may have been too hasty here - i have noticed that i now get this screen sometimes when i am not yet connected - shouldn't there be some sort of lock to not process if the session is not connected yet?
Append By: WindSurfer  When: 1998-07-24 07:26:07  New Status: Pending Customer
Comment If it takes more than 5 seconds for the screen to come up after LU initialization, then this could happen. Any details on what occurs when this pops-up? Is it related to a long initialization of the LU?
Append By: PeteL  When: 1998-07-27 08:44:03  New Status: Pending IE
Comment It's possible, but since I backed it out, I can't be sure. 5 seconds is a very long time, and it's not likely that this would be happening in our production system, which is where we're doing almost all our work. Could the difference be that in my definition I have to check all 24 lines, so that maybe you're being triggered by some other type of unformatted "screen" that isn't a full screen buffer, during some handshaking?
Append By: WindSurfer  When: 1998-07-27 09:44:48  New Status: Pending Customer
Comment Could be--any chance of getting a buffer trace? There might be a buffer that is being incorrectly interpreted as the blank screen, such as a write with no data, but no clear...on top of a screen that is just fine.
Append By: PeteL  When: 1998-07-28 08:10:01  New Status: Pending IE
Comment connect data flow trace sent via email 7/28 8:00am
Append By: PeteL  When: 1998-07-28 08:11:12  New Status: Pending IE
Comment BTW, the "LAST CHANGED" datestamp on SupportCenter is not accurate
Append By: WindSurfer  When: 1999-01-05 16:50:02  New Status: Pending Customer
Comment Can you please retest with latest build, as the code involved was updated in build 1.3.28.
Append By: PeteL  When: 1999-01-19 11:05:02  New Status: Closed
Comment Initial testing looks good - I'll close, but re-open if it fails when installed to production.
Append By: PeteL  When: 1999-02-08 13:14:56  New Status: Pending IE
Comment I just got a failure again - it is an almost blank screen, but it has an error message on line 24, starting in column 2 or 3 - WHEN SCREEN IS EMPTY is being driven, when in fact the screen isn't empty. I switched back to my settings when all 24 lines are compared to 80 blanks, and it worked fine.
Append By: WindSurfer  When: 1999-02-08 13:23:29  New Status: Pending Customer
Comment This can happen when there are multiple buffers sending unformatted displays-- last one doesn't clear, just sets cursor to 1,1.

Will try to make this more reliable...

Append By: WindSurfer  When: 1999-02-08 13:31:10  New Status: Pending Customer
Comment Any chance of a trace including this occurring?

This would help assure that we nail it.

Append By: PeteL  When: 1999-02-08 13:49:39  New Status: Pending IE
Comment yes, once I get through the wierdness I'm experiencing at the moment I'll get back to that and get you a trace - pretty sure I can recreate easily.
Append By: PeteL  When: 1999-02-09 08:42:56  New Status: Pending IE
Comment trace sent via email today, 2/9