Given your description, part of your problem is that CP is looking at your input before Linux gets it. The # problem can probably be solved by (and can open other problems by) issuing the command #CP TERM LINEND OFF. This will cause CP to quit intercepting # and turning it into a new line. Of course, it also keeps you from entering any more CP commands in the session while Linux is up. Actually, the " issue may be the same thing. The command #CP TERM ESCAPE OFF would keep it from being misinterpreted.
Or.... You could enter the characters as "" and "# so that they'd get to Linux unharmed. (That's the purpose of the escape character, after all.) You'd just have to remember to do this extra escaping, along with any that Linux needed for its own amusment. Note too that there are chardel, linedel and tabchar characters to deal with as well. In a CMS session, execute the command Q TERM to see their settings. It's interesting that most of these go back to the time before the 3270 for use in line editing on other terminals... vi is definitely out. This is because VT100 terminals interact with the system on a character by character basis, but the 3270 terminal works in "blocks". Your keystrokes are not seen by the host (in this case, Linux) until an attention key is pressed, such as the Enter key. vi is completely based on a character by character interaction. Any other program that expects to be able to immediately react to the keyboard (less, more...) are also crippled because of the choice of terminal. However, sed will work perfectly (given the escape quoting described above). And where more won't work well, cat works perfectly, because the screen freezes at the end of each page, waiting on you to press clear. Rather than trying to bend this environment to match others, you/we have to bend a bit to meet in a middle ground. ---- Robert P. Nix internet: [EMAIL PROTECTED] Mayo Clinic phone: 507-284-0844 RO-CE-8-857 page: 507-270-1182 200 First St. SW Rochester, MN 55905 ---- "Codito, Ergo Sum" "In theory, theory and practice are the same, but in practice, theory and practice are different." > -----Original Message----- > From: Eric Sammons [SMTP:[EMAIL PROTECTED] > Sent: Monday, June 16, 2003 6:41 AM > To: [EMAIL PROTECTED] > Subject: Questions regarding single user mode and z/VM > > I am new to this group as well as (what we have come to call) zLinux > running on z/VM. However, I was tasked with the POC (Proof of Concept) > project given my strong Linux and Unix background. Our POC involves an > installation of z/VM 4.3 and Suse Linux SLES - Timer 7.2. In working in > this environment the first thing I notice are issues around z/VM and Linux > in single user mode. These issues include the following: > > -> vi is out > -> paging (less / more) is out > -> " == Escape character in regex statements v. \ > -> # == NL in regex > > It seems all of these issues are tied to the simple issue of terminal > emulation. Given my background with Unix I certainly understand that > single user mode is a must for any Linux (Unix) installation. The reasons > to be able to support your VM (guest install) from single user mode is too > numerous to list as is the case with Unix installed anywhere. > > Has anyone else seen these problems and are their ways to fix them (the > issues)? I have figured out how to get around them with some interesting > perl commands, vi <file> << EOF statements, and sed commands. Now rather > than be crafty I would like to actually be able to do my job the way I can > on any other platform. > > Thanks! > > Eric Sammons > (804)697-3925 > FRIT - Infrastructure Engineering
