3270 input to zipl boot menu
I'm using zipl version 1.3.1 and am unable to send input to the boot loader via a 3270 terminal emulator. I'm using the following script to send input to the VM user: 1 /*Send case-insensitive commands to linux on LINUXVM*/ 2 Trace Off 3 Address Command 4 Parse Arg Command 5 'EXECIO 0 CP (SKIP STRING SEND LINUXVM' Command 6 Exit Rc which works fine once the kernel is up. I can log in, issue linux commands, etc. However, when I'm at the bootloader menu prompt, the script has no effect and I'm unable to load a non-default kernel or pass boot parameters. I'm a complete newbie to the VM world, so I'm not sure what's going on here. Does anyone have any ideas? Thanks, Brian -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: 3270 input to zipl boot menu
Your EXEC is using the SCIF (Secondary Console Input Facility) which lets you send and receive commands from a machine that you are set as the SECUSER (secondary user).Try passing this command to the boot loader: send cp linuxvm vi vmsg 0 You may have to play with the exec a little. Your exec as coded only sends virtual machine commands to LINUXVM. You need to send a CP console function command. SEND CP LINUXVM will send the cp command to linuxvm. vi vmsg will pass the command to the boot loader as if it were command from the hardware console. David Kreuter -Original Message- From: Linux on 390 Port on behalf of Brian Nelson Sent: Wed 3/22/2006 10:29 AM To: LINUX-390@VM.MARIST.EDU Subject: 3270 input to zipl boot menu I'm using zipl version 1.3.1 and am unable to send input to the boot loader via a 3270 terminal emulator. I'm using the following script to send input to the VM user: 1 /*Send case-insensitive commands to linux on LINUXVM*/ 2 Trace Off 3 Address Command 4 Parse Arg Command 5 'EXECIO 0 CP (SKIP STRING SEND LINUXVM' Command 6 Exit Rc which works fine once the kernel is up. I can log in, issue linux commands, etc. However, when I'm at the bootloader menu prompt, the script has no effect and I'm unable to load a non-default kernel or pass boot parameters. I'm a complete newbie to the VM world, so I'm not sure what's going on here. Does anyone have any ideas? Thanks, Brian -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: 3270 input to zipl boot menu
Brian Nelson [EMAIL PROTECTED] wrote on 22.03.2006 16:29:16: I can log in, issue linux commands, etc. However, when I'm at the bootloader menu prompt, the script has no effect and I'm unable to load a non-default kernel or pass boot parameters. Did you make sure to prefix boot loader prompt input with '#cp vinput vmsg' (see man zipl.conf)? Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on zSeries Development IBM Development Lab, Boeblingen/Germany -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: 3270 input to zipl boot menu
Hi DK, Actually, Brian and I are working on this together - CP is actually getting the VINPUT command but evidently doesn't know how to pass it to the Linux OS, we get: HCPPCX6531E The operating system will not accept commands from the service processor. Does anything special need to be enabled (either in the virtual machine or Linux kernel) to allow responses made via VINPUT to be received by the guest OS? Michael Coffin, VM Systems Programmer Internal Revenue Service - Room 6527 Constitution Avenue, N.W. Washington, D.C. 20224 Voice: (202) 927-4188 FAX: (202) 622-6726 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Kreuter Sent: Wednesday, March 22, 2006 11:23 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: 3270 input to zipl boot menu Your EXEC is using the SCIF (Secondary Console Input Facility) which lets you send and receive commands from a machine that you are set as the SECUSER (secondary user).Try passing this command to the boot loader: send cp linuxvm vi vmsg 0 You may have to play with the exec a little. Your exec as coded only sends virtual machine commands to LINUXVM. You need to send a CP console function command. SEND CP LINUXVM will send the cp command to linuxvm. vi vmsg will pass the command to the boot loader as if it were command from the hardware console. David Kreuter -Original Message- From: Linux on 390 Port on behalf of Brian Nelson Sent: Wed 3/22/2006 10:29 AM To: LINUX-390@VM.MARIST.EDU Subject: 3270 input to zipl boot menu I'm using zipl version 1.3.1 and am unable to send input to the boot loader via a 3270 terminal emulator. I'm using the following script to send input to the VM user: 1 /*Send case-insensitive commands to linux on LINUXVM*/ 2 Trace Off 3 Address Command 4 Parse Arg Command 5 'EXECIO 0 CP (SKIP STRING SEND LINUXVM' Command 6 Exit Rc which works fine once the kernel is up. I can log in, issue linux commands, etc. However, when I'm at the bootloader menu prompt, the script has no effect and I'm unable to load a non-default kernel or pass boot parameters. I'm a complete newbie to the VM world, so I'm not sure what's going on here. Does anyone have any ideas? Thanks, Brian -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: 3270 input to zipl boot menu
Nothing unusual: Kernel command line: root=/dev/dasda1 selinux=0 TERM=dumb elevator=cfq BOOT_IMAGE=1 No unusual options in the directory. OPTION RMCHINFO MAINTCCW set. What happens when you issue this logged onto LINUXVM? Eliminate the CP SEND. David -Original Message- From: Linux on 390 Port on behalf of Coffin Michael C Sent: Wed 3/22/2006 1:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: 3270 input to zipl boot menu Hi DK, Actually, Brian and I are working on this together - CP is actually getting the VINPUT command but evidently doesn't know how to pass it to the Linux OS, we get: HCPPCX6531E The operating system will not accept commands from the service processor. Does anything special need to be enabled (either in the virtual machine or Linux kernel) to allow responses made via VINPUT to be received by the guest OS? Michael Coffin, VM Systems Programmer Internal Revenue Service - Room 6527 Constitution Avenue, N.W. Washington, D.C. 20224 Voice: (202) 927-4188 FAX: (202) 622-6726 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Kreuter Sent: Wednesday, March 22, 2006 11:23 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: 3270 input to zipl boot menu Your EXEC is using the SCIF (Secondary Console Input Facility) which lets you send and receive commands from a machine that you are set as the SECUSER (secondary user).Try passing this command to the boot loader: send cp linuxvm vi vmsg 0 You may have to play with the exec a little. Your exec as coded only sends virtual machine commands to LINUXVM. You need to send a CP console function command. SEND CP LINUXVM will send the cp command to linuxvm. vi vmsg will pass the command to the boot loader as if it were command from the hardware console. David Kreuter -Original Message- From: Linux on 390 Port on behalf of Brian Nelson Sent: Wed 3/22/2006 10:29 AM To: LINUX-390@VM.MARIST.EDU Subject: 3270 input to zipl boot menu I'm using zipl version 1.3.1 and am unable to send input to the boot loader via a 3270 terminal emulator. I'm using the following script to send input to the VM user: 1 /*Send case-insensitive commands to linux on LINUXVM*/ 2 Trace Off 3 Address Command 4 Parse Arg Command 5 'EXECIO 0 CP (SKIP STRING SEND LINUXVM' Command 6 Exit Rc which works fine once the kernel is up. I can log in, issue linux commands, etc. However, when I'm at the bootloader menu prompt, the script has no effect and I'm unable to load a non-default kernel or pass boot parameters. I'm a complete newbie to the VM world, so I'm not sure what's going on here. Does anyone have any ideas? Thanks, Brian -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: 3270 input to zipl boot menu
Coffin Michael C [EMAIL PROTECTED] wrote on 22.03.2006 19:04:58: Actually, Brian and I are working on this together - CP is actually getting the VINPUT command but evidently doesn't know how to pass it to the Linux OS, we get: HCPPCX6531E The operating system will not accept commands from the service processor. This message indicates that the input to the boot loader prompt was not sent using the cp vi vmsg command. I'm not familiar with the cp send command, but did you implement David Kreuter's suggestion of using send cp linuxvm vi vmsg 0 instead of send linuxvm vi vmsg 0 ? Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on zSeries Development IBM Development Lab, Boeblingen/Germany -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: 3270 input to zipl boot menu
That did the trick. Thank you. On Mar 22 07:44PM, Peter Oberparleiter wrote: Coffin Michael C [EMAIL PROTECTED] wrote on 22.03.2006 19:04:58: Actually, Brian and I are working on this together - CP is actually getting the VINPUT command but evidently doesn't know how to pass it to the Linux OS, we get: HCPPCX6531E The operating system will not accept commands from the service processor. This message indicates that the input to the boot loader prompt was not sent using the cp vi vmsg command. I'm not familiar with the cp send command, but did you implement David Kreuter's suggestion of using send cp linuxvm vi vmsg 0 instead of send linuxvm vi vmsg 0 ? Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on zSeries Development IBM Development Lab, Boeblingen/Germany -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: zipl boot menu
Alle Tuesday 19 October 2004 01:09, hai scritto: I'm trying to use the menu functionality that zipl provides. It doesn't seem to make any difference in the way my system comes up. The output I get from zipl seems to indicate that when I reboot I'll get the menu, but instead it just immediately boots the default kernel. My /etc/zipl.conf file has this in it: [cut] Insert timeout=x , where x are the seconds of waiting before system comes up in defaul mode. Your zipl.conf menu1 will appear: [2.4.21] target=/boot image=/boot/image-2.4.21 parmfile=/boot/parmfile [2.4.26] target=/boot image=/boot/image-2.4.26 parmfile=/boot/parmfile :menu1 target=/boot 1=2.4.26 2=2.4.21 default=1 timeout=5 bye, -- G -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: zipl boot menu
Tuesday 19 October 2004 01:09, you wrote: I'm trying to use the menu functionality that zipl provides. It doesn't seem to make any difference in the way my system comes up. The output I get from zipl seems to indicate that when I reboot I'll get the menu, but instead it just immediately boots the default kernel. My /etc/zipl.conf file has this in it: [cut] Insert timeout=x , where x are the seconds of waiting before system comes up in defaul mode. Your zipl.conf menu1 will appear: [2.4.21] target=/boot image=/boot/image-2.4.21 parmfile=/boot/parmfile [2.4.26] target=/boot image=/boot/image-2.4.26 parmfile=/boot/parmfile :menu1 target=/boot 1=2.4.26 2=2.4.21 default=1 timeout=5 bye, -- G -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: zipl boot menu
Post, Mark K [EMAIL PROTECTED] wrote: [...] instead it just immediately boots the default kernel. My /etc/zipl.conf *cough*man zipl.conf*cough* If the 'prompt' setting of the menu section is set to 1, a menu text will be displayed during IPL and the boot program will wait for user input: [...] If the 'timeout' option has been used, the boot menu will automatically start the default configuration after the specified number of seconds has passed without user input. [...] The loadparm function is available even if the menu has been deacti- vated by setting 'prompt' to zero or by installing only a single con- figuration. The menu can then be temporarily activated by passing the string 'prompt' via the loadparm function: #cp ipl 0192 loadparm prompt Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on zSeries Development IBM Development Lab, Boeblingen/Germany -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: zipl boot menu
Tuesday 19 October 2004 01:09, you wrote: I'm trying to use the menu functionality that zipl provides. It doesn't seem to make any difference in the way my system comes up. [cut] Insert timeout=x , where x are the seconds of waiting before system comes up in defaul mode. Your zipl.conf will appear: [2.4.21] target=/boot image=/boot/image-2.4.21 parmfile=/boot/parmfile [2.4.26] target=/boot image=/boot/image-2.4.26 parmfile=/boot/parmfile :menu1 target=/boot 1=2.4.26 2=2.4.21 default=1 timeout=5 bye, -- Gian -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: zipl boot menu
I did read the man page, several times. I should have mentioned that I'm using s390-tools 1.2.4. The text you quote does not appear in the man page at that level. If I try to specify either prompt or timeout in the menu section, zipl complains about an unknown keyword, and won't run. So, any advice as to how to get this to work with 1.2.4? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter Oberparleiter Sent: Tuesday, October 19, 2004 4:30 AM To: [EMAIL PROTECTED] Subject: Re: zipl boot menu Post, Mark K [EMAIL PROTECTED] wrote: [...] instead it just immediately boots the default kernel. My /etc/zipl.conf *cough*man zipl.conf*cough* If the 'prompt' setting of the menu section is set to 1, a menu text will be displayed during IPL and the boot program will wait for user input: [...] If the 'timeout' option has been used, the boot menu will automatically start the default configuration after the specified number of seconds has passed without user input. [...] The loadparm function is available even if the menu has been deacti- vated by setting 'prompt' to zero or by installing only a single con- figuration. The menu can then be temporarily activated by passing the string 'prompt' via the loadparm function: #cp ipl 0192 loadparm prompt Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on zSeries Development IBM Development Lab, Boeblingen/Germany -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: zipl boot menu
Post, Mark K [EMAIL PROTECTED] wrote: I did read the man page, several times. I should have mentioned that I'm using s390-tools 1.2.4. The text you quote does not appear in the man page at that level. If I try to specify either prompt or timeout in the menu section, zipl complains about an unknown keyword, and won't run. So, any advice as to how to get this to work with 1.2.4? Unfortunately not. Boot menu support was only added in s390-tools version 1.3.0. Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on zSeries Development IBM Development Lab, Boeblingen/Germany -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: zipl boot menu
Then let me register a retroactive complaint, for future reference. Don't put things in the man page that aren't supported in the software. It only confuses people, and wastes a lot of time, both on their part, and the mailing list. I'll install 1.3.0 and see if I have better luck there. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter Oberparleiter Sent: Tuesday, October 19, 2004 11:33 AM To: [EMAIL PROTECTED] Subject: Re: zipl boot menu Post, Mark K [EMAIL PROTECTED] wrote: I did read the man page, several times. I should have mentioned that I'm using s390-tools 1.2.4. The text you quote does not appear in the man page at that level. If I try to specify either prompt or timeout in the menu section, zipl complains about an unknown keyword, and won't run. So, any advice as to how to get this to work with 1.2.4? Unfortunately not. Boot menu support was only added in s390-tools version 1.3.0. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: zipl boot menu
Post, Mark K [EMAIL PROTECTED] wrote: Then let me register a retroactive complaint, for future reference. Don't put things in the man page that aren't supported in the software. It only confuses people, and wastes a lot of time, both on their part, and the mailing list. I'll install 1.3.0 and see if I have better luck there. While I admit that the wording of the respective man-pages is somewhat vague, I don't agree with your statement that the man page describes a feature which is not supported by the software: The man page of zipl versions 1.2.0-1.2.4 contain references to a feature which allows specifying multiple boot configurations with the addition that: If supported by the hardware, an interactive choice of these configurations will be available at boot time, otherwise the menu's default entry is booted. Hardware support in this context refers to the extended HMC panel used during IPL from SCSI devices. This panel contains an extra input field that can be used to specify a non-default boot configuration. I guess it's this section together with the ambiguity of the term menu that caused the misunderstanding (I'll try to keep the text more clearer in the future). Anyway, I hope that with the new version, the feature works as expected for you. Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on zSeries Development IBM Development Lab, Boeblingen/Germany -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
zipl boot menu
I'm trying to use the menu functionality that zipl provides. It doesn't seem to make any difference in the way my system comes up. The output I get from zipl seems to indicate that when I reboot I'll get the menu, but instead it just immediately boots the default kernel. My /etc/zipl.conf file has this in it: # cat /etc/zipl.conf [2.4.21] target=/boot image=/boot/image-2.4.21 parmfile=/boot/parmfile [2.4.26] target=/boot image=/boot/image-2.4.26 parmfile=/boot/parmfile :menu1 target=/boot 1=2.4.26 2=2.4.21 default=1 The output from the zipl command is this: # zipl -m menu1 Using config file '/etc/zipl.conf' Building bootmap '/boot/bootmap' Building menu 'menu1' Adding #1: IPL section '2.4.26' (default) Adding #2: IPL section '2.4.21' Preparing boot device: dasdg (0206). Done. I'm running on z/VM 5.1. Does anyone have any ideas why this isn't working? Thanks, Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
