Hi Roland,
There are two places you must specify the console address. First off, you have to tell the hardware. That is what you are seeing on the Support Element console. For the IPL address, you use your dasd device address. For the Loadparm, just enter the device address of the terminal you want to use for the console. IPL the processor. SAPL should come up on the device you entered in the Loadparm field. At that point you can enter cons=xxxx to tell VM where to find the console, and continue with the VM IPL.
Peter
-----Original
Message-----
Hi All, thanks for all your responses. How could I forget the SAPL. Must be getting old....
The customer is still using VM/ESA 2.30... I don't know if the SAPL would take the LOADPARM. Anyway, the application runing on the MP2003-204 allows a place to put in a load address and a load parameter. However, it only allows 8 characters in this load parameter field, but NO special characters allows, like the = sign... RRRRRRRrrrrrr......
There are no "intergrated console support" in this beast either....
Do you have other suggestions? TIA
Regards,
...Roland
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error, please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail, or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner. |
- Re: IOCP for MP2003-204 Roland P. Chung
- Re: IOCP for MP2003-204 David Boyes
- Re: IOCP for MP2003-204 Richard Corak
- Re: IOCP for MP2003-204 Alan Altmark
- Re: IOCP for MP2003-204 Roland P. Chung
- Re: IOCP for MP2003-204 Rob van der Heij
- Re: IOCP for MP2003-204 Shimon Lebowitz
- Re: IOCP for MP2003-204 Kris Buelens
- Re: IOCP for MP2003-204 Imler, Steven J
- Re: IOCP for MP2003-204 Roland P. Chung
- Re: IOCP for MP2003-204 Peter . Webb
- Re: IOCP for MP2003-204 Kris Buelens
- Re: IOCP for MP2003-204 George Haddad
- Re: IOCP for MP2003-204 George Haddad
- Re: IOCP for MP2003-204 Roland P. Chung
- Re: IOCP for MP2003-204 George Haddad
- Re: IOCP for MP2003-204 Roland P. Chung
- Re: IOCP for MP2003-204 Roland P. Chung
- Re: IOCP for MP2003-204 George Haddad
- Re: IOCP for MP2003-204 Eric Schadow
- Re: IOCP for MP2003-204 Steve Gentry