Making your Remote Development Program (RDP) zOS Available for Logon
Please reference the information initially sent to notify you that your zOS operating system was ready for use. It should have included several ids available for your use in the IIC-Dallas environment. This document will hopefully help you understand our environment more clearly so you can more easily bring your zOS operating system up and running.
A Simple Way of Looking at Our Environment
-
The zVM system is an operating system which emulates many different types of operating systems and can run many of these systems simultaneously.
-
Consider each id you received as an operating system which runs on the zVM computer. You can also think of each id as a PC which can be customized to your requirements. If you can picture the zVM operating system as your home and each id as a “GUEST’ in your home, you have it because each id is also called a VM Guest userid.
-
At this time MOST ids which begin with “ETPGM” are zOS operating system ids. This is the id that contains the zOS operating system where you can logon to TSO or other applications you may develop. It is also called the zOS Guest system id. Please note: You DO NOT logon to this is id.
-
The other ids you received are used by you or other members of your group to logon to the zVM system to maintain the zOS operating system id. These other ids are used to execute the “SVXLOG” command. The SVXLOG command allows you to Initial Program Load (IPL) or “BOOT” the id mentioned in Step 3.
Please note: These are NOT TSO userids, to add userids for TSO and USS access follow the procedures here to define TSO userids..
Example
Your zOS system name is “ETPGMXX” and you received a userid of “ETPURDP” for your use.
You would first logon to the zVM system using the userid “ETPURDP” as shown in the “Example IPL Process” later in this document.
Once you have logged on as “ETPURDP”, to make your zOS operating system available for use, you IPL or BOOT the zOS operating system by typing the following command.
SVXLOG ETPGMXX
IPL Walkthrough
In this walkthrough, you will need:
-
an SSLV3-capable TN3270 emulator.
Note: You will require a Certificate Authority (CA) certificate to logon to the following IP Address. Many of our ISVs use PCOMM as their preferred TN3270 emulator. We have included instructions for installing the certificate at IIC-Dallas CA Certificate Instructions.
These will serve as an example for those NOT using PCOMM, but using a SSLV3 capable TN3270 emulator
-
a zVM Guest userid: ETPURDP
-
a zOS Guest system id: ETPGMXX
Connection Information
-
IP Address:
198.81.193.6 -
Port:
23 -
SSL: Enabled
Initial Login
You will see a IIC-Dallas Login Screen:

Type DR2 and press ENTER.
Next, You will see a zVM Online Logon screen:

Enter your credentials:
Fill in your USERID and PASSWORD and press ENTER
(Your password will not appear when you type it)
USERID ===> ETPURDP
PASSWORD ===> PasswordFor ETPURDP
COMMAND ===>
Press ENTER.
After Login
You will receive many messages on your emulator screen after login. Continue clearing your screen by pressing enter until you see:
Running SVSCDR2
On the lower right-hand corner of your emulator screen.
You are now ready to IPL ETPGMXX, the z/OS Guest System.
IPL the zOS Guest System
Run:
===> SVXLOG ETPGMXX
Press ENTER.
You will receive many messages and must clear the screen repeatedly. Pay attention to any prompts which MAY require you to respond to so the system can complete the IPL. When you stop receiving messages from your zOS Guest System, we recommend you send the following command to make sure there are NO outstanding replies which MAY need your action before the IPL or “Boot” is successfully completed.
===> SEND ETPGMXX \CP VI VMSG D R,L
If all went well, you should receive a message like
ETPGMXX : IEE112I 10.25.57 PENDING REQUESTS 863
ETPGMXX : RM=0 IM=0 CEM=0 EM=0 RU=0 IR=0 NOAMRF
ETPGMXX : NO MESSAGES OUTSTANDING
Otherwise, you must respond to any outstanding message with the following syntax, where xx is the message number and YourResponse is an option included in the outstanding reply message.
===> SEND ETPGMXX \CP VI VMSG xx,YourResponse
Then hit ENTER
Example: I executed the d r,l command and received an outstanding message number 01 with the option to reply Y for YES or N for NO to continue processing. I want the system to continue processing, so I would respond as follows:
===> SEND ETPGMXX \CP VI VMSG 01,yThen hit ENTER
Activate the zOS Console
Once you have no outstanding responses, start your system's base applications with the following command:
===> SEND ETPGMXX \CP VI VMSG S ALL
Then hit ENTER.
Your system should now be available for you to logon to TSO. If your system is NOT configured to automatically start certain applications, you may need to start them manually
Some Example Commands to send to your zOS Guest
To check outstanding replies: SEND ETPGMXX \CP VI VMSG D R,L
To respond to a reply: SEND ETPGMXX \CP VI VMSG 01,y
To start most applications: SEND ETPGMXX \CP VI VMSG S ALL
To start TCPIP: SEND ETPGMXX \CP VI VMSG S TCPIP
To start TN3270: SEND ETPGMXX \CP VI VMSG S TN3270
To start INETD: SEND ETPGMXX \CP VI VMSG S INETD
To execute JES2 command: SEND ETPGMXX \CP VI VMSG $djxxxxx
To display active tasks: SEND ETPGMXX \CP VI VMSG d a,l