Re: [CMS-PIPELINES] Browse, Experimental device driver

2016-11-04 Thread Amphitryon
Am 31.10.2016 um 16:49 schrieb Hobart Spitz: > [...] > (Why use CC on a non-printer? To get underscores and some color. Try it.) For two days I thought the attributes '(* * * * * * 0' would do the trick and make 'browse' use the same codepage as term/cons or xedit. Now with option CC - drum-rol

Re: [CMS-PIPELINES] Browse, Experimental device driver - solved

2016-11-02 Thread Amphitryon
Problem solved, by reading documentation and little testing. But first I took the far distance deviation over extracting FPLRICBW REXX (15 Dec 2007 12:36:31) from PIPELINE MODULE. So I found BROWSE/BRW does not mind what is set as NONDISP character (00-3f and ff are set to blank), and only 8 of 9

Re: [CMS-PIPELINES] Browse, Experimental device driver

2016-11-01 Thread Amphitryon
To the Senior Managing 3270 Codepage Dark Arts Instructor Dear Sir, most respected Esquire, thank you to shed some light on this darkest site of my knowledge, I will do bestir myself and bring Browse to work flawlessly also on PersComm as it did so far on Mochasoft's tn3270. Best, Mike Salutati

Re: [CMS-PIPELINES] Browse, Experimental device driver

2016-11-01 Thread Alan Altmark
On Tuesday, 11/01/2016 at 05:02 GMT, amphitr...@ok.de wrote: > Drawback, what is shown as bullet point in Xedit and by cons/term > shows as little upper 3 with browse. G! But only on a more > up-to-date 3270. Again g!! with more emphasis. You need to know what codepage your display is and

Re: [CMS-PIPELINES] Browse, Experimental device driver

2016-11-01 Thread Amphitryon
Thank you for your prompt reply. > Your application can parse the output of DIAGNOSE 0x8C (REXX diag('8C') > BIF) to discover the code page of the terminal and use that value on > TERMCODEPAGE. I will dig a bit deeper in this direction. Gets thrilling. :) >> ... And if I set CMS fullscreen on, i

Re: [CMS-PIPELINES] Browse, Experimental device driver

2016-11-01 Thread Alan Altmark
On Tuesday, 11/01/2016 at 04:22 GMT, amphitr...@ok.de wrote: > > Browse, on the other hand, is full screen. Be careful what kind of data < > > 0x40 you send to pipelines full screen stages. > > In other words, it is my fault that some codepoints turn out > different by cons/term and browse. In t

Re: [CMS-PIPELINES] Browse, Experimental device driver

2016-11-01 Thread Amphitryon
Hello Hobart! > I use BROWSE often. At the risk of throwing a monkey wrench into the > works, I'll add a few comments. Thank you for writing down what I thought. Well, your first point may be a bit special, I regard browse first as data-presenter for interactive applications. But if it helps al

Re: [CMS-PIPELINES] Browse, Experimental device driver

2016-11-01 Thread Amphitryon
Hello Alan > The cons/term stage is 3215 line mode. [...] > CP does not assume a particular code page. As such I regard this as accurate, if the 3270 emulation on my PC is set up correctly. > Browse, on the other hand, is full screen. Be careful what kind of data < > 0x40 you send to pipelines

Re: [CMS-PIPELINES] Browse, Experimental device driver

2016-10-31 Thread Hobart Spitz
I use BROWSE often. At the risk of throwing a monkey wrench into the works, I'll add a few comments. First, BROWSE hangs on a disconnected machine. When I think there is a chance of, that I use a wrapper that chooses between CONS and BROWSE based on the connectedness of the current user machine.

Re: [CMS-PIPELINES] Browse, Experimental device driver

2016-10-31 Thread Alan Altmark
On Monday, 10/31/2016 at 02:26 GMT, amphitr...@ok.de wrote: > As Pipelines touches almost everything VM/CMS I assume following > question is appropriate within this list, albeit it is somewhat > related to 3270 emulations too. > > Until this weekend I assumed the display from > > > pipe(sep !)xrang

[CMS-PIPELINES] Browse, Experimental device driver

2016-10-31 Thread Amphitryon
As Pipelines touches almost everything VM/CMS I assume following question is appropriate within this list, albeit it is somewhat related to 3270 emulations too. Until this weekend I assumed the display from > pipe(sep !)xrange 40-ff!fblock 16!term and > pipe(sep !)xrange 40-ff!fblock 16!brw wo