Title: 2nd level test system problems

After you define your virtual 3270 addresses first-level (SPECIAL vdev 3270 in the CP directory or CP DEF GRAF vdev  from command line)

IPL your 2nd-level system and on 2nd-level OPERATOR  do, for each vdev address you defined above:

cp set rdevice Vdev type 3270_display

then CP ENABLE ALL

then try DIAL -ing

 


This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments.  Please notify the sender immediately by reply e-mail and delete the e-mail from your system.

-----Original Message-----

From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Clark, Carl
Sent: Monday, October 31, 2005 3:06 PM
To: [email protected]
Subject: 2nd level test system problems

 

VM enthusiasts:

   Thanks for all the answers about saving CMS for the 2nd Level system and about a disk mapping utility.

Have any of you installed a 2nd level VM by using the guidelines in SC24-6115 Running Guest Operating Systems?  I am stuck after the IPL because I have no CMS available to the 2nd-level Operator user.  You nice folks told me to add an NSS of CMS using the Maint user on the 2nd-level but I cannot dial in to this system since we have no real 3270 devices here,  and since I don't have TCP/IP installed I cannot use Telnet.

Any ideas on where I should go from here?  Should I forego this attempt and use the install procedure that came with our initial install from tapes (14 no less) ?

Your help is appreciated,
Carl Clark
BCBST

Please see the following link for the BlueCross BlueShield of Tennessee E-mail
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm


Reply via email to