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. The part that gets tricky is when CC (honor ASCII carriage control in column 1) is coded. You don't want overstrikes going to the console twice, nor do you want underscores displayed on a separate line, so there is extra code for that. (Why use CC on a non-printer? To get underscores and some color. Try it.) Second, it would be great if BROWSE would honor CMS WINDOWS configurations and display like other CMS WINDOWS "aware" software. Third, it would be nice if there were some way to configure the PF and other action keys, and to have it exit due to an external event, esp. a DELAY expiration. Thus you could have auto-refresh of a display, and have key actions other than those that are already hardcoded. Fourth, the FIND/REPEAT function is severely limited, in two ways. It is strictly case sensitive, and there is no indication, by highlighting and/or cursor positioning, of the location on the screen where the FIND stopped, or why (found or EOF e.g.). This makes it less than ideal for end-user applications. The point, in essence, is that BROWSE is a useful, valuable stage that is worthy of various enhancements, and which would be even better with them. Unlike the XEDIT stage, the entire file does not have to be read into guest storage, and display starts as soon as the first screen is filled up. I think BROWSE deserves to be upgraded from an experimental stage to a regular stage On Sun, Oct 30, 2016 at 7:33 PM, <[email protected]> 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 !)xrange 40-ff!fblock 16!term > > and > > > pipe(sep !)xrange 40-ff!fblock 16!brw > > would look similar on any single display. Alas it depends which > TN3270 emulation I use there are considerable differences on many > codepoints (the colours are not a problem). The options and > attributes I tried did not help too much. > > Question: how may I ensure the browse stage to use the same > codepage like Xedit or fullcreen cms on every 3270? > > Up to now I used BRW with the attribute 06X to get yellow letters > on black background, and with 'X' a for sure nonexistent > programmed symbol set assuming this would enforce the default. > Wrong, a better 3270 emulation displayed nothing but PROG753 and > blocked. > > Addendum to the above question: How may I ensure yellow on black > (or if not possible a default setting) without _for sure not_ > blocking any terminal? > > Regarding colours, I assumed BRW without attributes uses defaults > for highlighting, colour and PSS, but BRW (000000 displays in a > different colour on one screen. From the description: Use X'00' to > select the default attribute value depending on the terminal. > > To make it non-ambiguous and clear: my problem is the difference > between display of special characters between Xedit or Type or > PIPE...!term on the one hand and PIPE...!BRW otherwise. Quite > possible you observe no difference as I did until yesterday. The > difference between one terminal or 3270 emulator to others is > another subject. > > Ciao.....Mike > -- > www.Ok.de - die kostenlose E-Mail Adresse > -- OREXXMan
