Steps For Testing Your Automation - IBM ZVM - FOR LINUX V6 RELEASE 1 Getting Started

Result: The PROFILE EXEC looks like this:
/* Sample PROFILE EXEC for Linux servers */
"CP TERM LINEND %"
"CP SET PF12 RETRIEVE" /* Recall previous commands */
"CP TERM MORE 1 0"
"CP SET RUN ON"
"CP TERM HOLD OFF"
"ACCESS 592 Z"
"CP SET SECUSER OPERATOR" /* Operator is sec console*/
"CP IPL 150 CLEAR"
7.
Save the PROFILE EXEC. From the XEDIT command line, type this command
and press the Enter key:
====> file
8.
From the command line, type these commands and press the Enter key after
each one:
profile
%cp disconnect
9.
Repeat steps 1 to 8 for each Linux virtual machine.
Continue to the next procedure.

Steps for testing your automation

To test your automation, try to attempt to couple a network adapter that is already
coupled. Messages at the LGLOPR virtual console that the coupling fails tell you
that your automation is working properly.
Before you begin: You need to be logged onto LGLOPR and you must have at
least one Linux virtual server running.
Perform these steps to test your automation:
1.
Reset the terminal line end character for LGLOPR. From the command line,
type this command and press the Enter key:
term linend #
Ready;
2.
From the command line, type this command and press the Enter key:
#cp send userid %cp couple 600 system vswitch1
Where userid is the user ID of a Linux virtual server.
Result: You should see these failure messages on the LGLOPR virtual console,
which proves your automation is working:
Ready;
userid
WITCH SYSTEM
userid
/* Use %CP to talk to CP
/* Clear screen after 1 sec */
/* CP READ won't stop server*/
/* (Look in book)
/* Get to TCP/IP functions */
/* Load Linux automatically */
systemid: HCPCPL2788E NIC 0600 not connected; already connected to VS
systemid: .. VSWITCH1
*/
*/
Chapter 9. Setting up basic system automation
95