On Friday, 03/18/2011 at 05:07 EDT, "CHAPLIN, JAMES (CTR)" <james.chap...@associates.dhs.gov> wrote:
> But I thought I would try the same command from the guest console (#CP Q > DA), and got the following response just before the server rebooted: > > DASD 4886 ON DASD 4886 R/W VI1304 SUBCHANNEL = 014C > DASD 4887 ON DASD 4887 R/W VI1305 SUBCHANNEL = 014D > > Error: output (21282 bytes) was truncated, > > Two questions as I am a VM rookie, > > How to you modify the buffer from the console for the CP command? > How do you display the buffer size available for a CP command? You don't. The "Error: output" you see wasn't generated by CP; it came from Linux. Ergo, the command you issued didn't actually go to CP. It wouldn't surprise me if someone set up a shell script of some sort to turn #cp (a habit) into vmcp. > Why would a query command on a console bring down a linux guest, but > vmcp query does not? Is this a know bug? Try again, but issue vmcp query term before you try the #cp. I often see that the LINEND character has been set to something other than # in order to allow use of # in Linux. Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
