Lucius: The string provided by z/VM is terminated by a byte of binary zero, at least according to the CP Command and Utility Reference. If it is, it should be easy to find the end of the values supplied on IPL.I would recommend ensuring the high-order byte of GR0 is zero when the SAVESYS command is issued to create the NSS.
The "case thing" is a problem if you issue the IPL command manually. In an EXEC, you can pass the parameter value in the case you prefer. Romney On Wed, 5 Mar 2003 19:12:46 -0600 Lucius, Leland said: >Sorry, I took so long to get back. "Real" work go in the way of all my fun >today. I hate when that happens. ;-) > >> >> The patch seems to work, although I tend to get junk at the end of the >> parm line if I specify it, and the capitalization all goes away. >> >> For example, if I do >> >> ipl deb24m parm line VMPOFF='IPL CMS' >> >> what shows up is >> >> Kernel command line: root=/dev/dasd/0150/part1 ro noinitrd >> dasd=0150-015f vmpoff="LOGOFF" vmpoff='ipl cms'1 q >> >> So, what's that '1 q' doing at the end? And how can I make the parm >> line respect my capitalization (that's probably a CMS thing, >> isn't it?)? >> >When you did the DEFSYS, did you include the PARMREGS=0-15 parameter? >Leaving it off does work, but CP doesn't terminate the parms with a hex zero >which is required by the patch. Including PARMREGS=0-15 causes CP to clear >all registers to zero before loading the IPL PARMs. > >The case thing IS indeed a problem. It places some restrictions on what can >be included in the IPL PARMs. CP seems to convert the entire command line >to uppercase before processing it. Unfortunately, most kernel parameters >are expected to be in lowercase. So, the patch converts the parms to >lowercase when appending to the kernel parameters. I wish I knew a way to >get around it, but I couldn't find anything in the books. > >Leland
