VM/Pass-Through Facility - IBM · of IBM systems, consult the latest IBM System/370, 30xx, 4300,...

5/31/2019 IBM Library Server Print: dvma1a00

https://www.ibm.com/support/libraryserver_os390/PRINT?Book=dvma1a00&DT=19911105145642&C=4&PRINTALL=All+topics&BookNotes=1 1/71

IBM Library Server

DOCNUM = SC24-5555-00 DATETIME = 11/05/91 14:56:42

BLDVERS = 1.2 TITLE = User's Guide

AUTHOR = COPYR = © Copyright IBM Corp. 1991

PATH = /home/webapps/epubs/htdocs/book

VM/Pass-Through Facility

User's Guide

Version 2

Document Number SC24-5555-00

Program Number 5684-100

File Number S370/4300-39

NOTICES Notices ___ Note! __________________________________________________________ | | | Before using this information and the product it supports, be sure | | to read the general information under "Notices" in topic FRONT_1. | | | |____________________________________________________________________|



EDITION Edition Notice First Edition (September 1991)

This edition, SC24-5555-00, applies to Version 2 of the VM/Pass-Through Facility licensed program (Program Number 5648-100) and to all subsequent versions and modifications until otherwise indicated in new editions or Technical Newsletters. It contains material formerly included in VM/Pass-Through Facility Managing and Using, GC24-5206. Changes are made periodically to the information herein; before using this publication in connection with the operation of IBM systems, consult the latest IBM System/370, 30xx, 4300, and 9370 Processors Bibliography, GC20-0001, for the editions that are applicable and current.

Publications are not stocked at the address given below. Requests for IBM publications should be made to your IBM representative or to the IBM branch office serving your locality.

A form for reader's comments is provided at the back of this publication. If the form has been removed, comments may be addressed to IBM Corporation, Information Development, Dept. G60, P.O. Box 6, Endicott, NY, U.S.A., 13760. IBM may use or distribute whatever information you supply in any way it believes appropriate without incurring any obligation to you.

The form for readers' comments provided at the back of this publication may also be used to comment on the VM online HELP facility.

© Copyright International Business Machines Corporation 1991. All rights reserved. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.

CONTENTS Table of Contents Summarize COVER Book Cover NOTICES Notices EDITION Edition Notice CONTENTS Table of Contents FRONT_1 Notices FIGURES Figures



TABLES Tables FRONT_2 Trademarks and Service Marks PREFACE Preface PREFACE.1 What This Book Contains PREFACE.2 How User Entries and Command Names Are Shown PREFACE.3 Where to Find More Information 1.0 Introduction 1.1 Using the VM/Pass-Through Facility Version 2 1.2 What's New in this Version? 1.3 Getting Online HELP 2.0 Part 1: Accessing PVM and Establishing Sessions 2.1 The PVM Initial Menu 2.1.1 Initial Menu Explanations 2.2 The CP DIAL Command 2.3 The VTAM LOGON Command 2.4 The PASSTHRU Command 2.4.1 Working with the PASSTHRU Command 2.4.1.1 Helpful Tips for Using the PASSTHRU Command 2.4.1.1.1 Switching Between Your Host and Target Session 2.4.1.1.2 Putting the PASSTHRU Command in a Small Exec 2.4.1.1.3 Creating Nicknames in Your CMS User ID NAMES File 2.4.1.1.4 Creating Synonyms in a CMS SYNONYM File 2.4.2 Using the PASSTHRU NOTEPAD Facility 2.5 The PVM Selection Menu 2.5.1 Selection Menu Explanations 2.6 The MPVM Command (Multiple Session Support) 2.6.1 Using the MPVM Selection Menu 2.6.1.1 Selection Menu Explanations 2.6.2 Working with the MPVM Command 2.6.2.1 Specifying Parameters with the MPVM Command 2.6.2.2 Using the MPVM Command with the Escaped Command Facility 2.6.3 Switching Among Multiple Active Sessions 2.6.3.1 Working with Your Host CMS Session 2.6.3.2 Using the WHERE Macro to Get Information about Sessions 2.6.4 Using the MPVM NOTEPAD Facility 2.6.4.1 Setting a PF Key as NOTEPAD 2.6.4.2 Setting Up Separate NOTEPAD Files 2.6.5 Creating a Personal MPVM NAMES File 2.6.5.1 Other :Nick. Tags 2.6.6 Setting PA, PF Keys, or SysReq Key 2.6.7 Changing Variable Settings 2.6.8 Issuing MPVM Commands 2.6.8.1 Specifying ?QUERY to Get Information About Sessions 2.6.9 Example: Multiple Session Activities 2.6.9.1 Putting Entries in a Personal MPVM NAMES File 2.6.9.2 Displaying Multiple Sessions 3.0 Part 2: Issuing PVM Server Commands 3.1 The CP SMSG Command 3.2 Issuing a Command to a Remote PVM or PVMG Node 3.3 Specifying a Language For Command Responses 3.4 The SHOW Command 3.5 The Query Command 3.6 The MSG and PMSG Commands 3.7 The CPQ Command 3.8 More Information on PVM and PVMG Server Commands



4.0 Part 3: Appendix, Glossary, Bibliography and Index A.0 Appendix. Recovering from a Program Error A.1 Screen Explanations A.2 Preventing Errors A.3 Requesting I/O Verification GLOSSARY Glossary BIBLIOGRAPHY Bibliography BIBLIOGRAPHY.1 PVM and Related Publications BIBLIOGRAPHY.1.1 VM/ESA (ESA Feature) Publications BIBLIOGRAPHY.1.2 VM/ESA (370 Feature) Publications BIBLIOGRAPHY.1.3 VM/ESA Common Publications INDEX Index COMMENTS Readers' Comments

FRONT_1 Notices References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectual property rights or other legally protectible rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, programs, or services, except those expressly designated by IBM, are the user's responsibility.

IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Commercial Relations, IBM Corporation, Purchase, NY 10577.

FIGURES Figures 1. You can access PVM and SNA networks using PVM's Gateway component 1.2 2. PVM Initial Menu 2.1 3. PVM Selection Menu 2.5 4. MPVM Selection Menu 2.6.1 5. Pat Smith's MPVM NAMES File Entries 2.6.9.1 6. Program Error Recovery Screen A.0

TABLES Tables



1. HELP Commands for Getting Online Help 1.3 2. Specifying Parameters with the PASSTHRU Command 2.4.1 3. How to Set PF, PA Keys or SysReq Key 2.6.6 4. General User MPVM Commands 2.6.8 5. General User PVM Server Commands 3.0

FRONT_2 Trademarks and Service Marks

The following terms, denoted by an asterisk (*) in this publication, are trademarks of the IBM Corporation in the United States and/or other countries:

Virtual Machine/Enterprise VM/ESA System Architecture Virtual Machine/Extended Architecture VM/XA Virtual Telecommunications Access Method VTAM System/370 PROFS

PREFACE Preface This book is for anyone who needs to access one or more systems in addition to their primary system and is intended for all VM/Pass-Through Facility users as a prerequisite to the following books:

° VM/Pass-Through Facility Administration and Operation (SC24-5557-00) ° VM/Pass-Through Facility Programming Reference (SC24-5556-00).

You should have some knowledge of VM's Conversational Monitor System (CMS). It is helpful to know:

° What a virtual machine is ° What a network is.

Subtopics:

PREFACE.1 What This Book Contains PREFACE.2 How User Entries and Command Names Are Shown PREFACE.3 Where to Find More Information

PREFACE.1 What This Book Contains

This book contains an introduction section and three parts:



_______________ ___________________________________________________________ | Introduction | Describes the VM/Pass-Through Facility Version 2 (PVM) | | | product and tells how to obtain online HELP. | | | | |_______________|___________________________________________________________| | Part 1 | Describes accessing PVM and establishing interactive | | | sessions. | | | | |_______________|___________________________________________________________| | Part 2 | Describes PVM server commands. | | | | | | | |_______________|___________________________________________________________| | Part 3 | Contains an appendix on how to recover from a program | | | error; a glossary, bibliography and index. | | | | |_______________|___________________________________________________________|

A reference card is included that summarizes information in this book.

PREFACE.2 How User Entries and Command Names Are Shown

User entries which you may enter at the console or include in a PROFILE EXEC are shown in blue. Uppercase letters in a command string indicate keywords or options you can specify. In addition, italics within a command string indicate a variable where you must substitute a value such as substituting MYFILE for filename.

Capitalized letters in a command name indicate the shortest abbreviation you can specify.

PREFACE.3 Where to Find More Information

Bibliography See topic BIBLIOGRAPHY for a listing of the titles and order numbers of all related publications.

Glossary See topic GLOSSARY for definitions of terms used in this book.

You can find additional information about VM/Pass-Through Facility Version 2 in the following books:

° VM/Pass-Through Facility Administration and Operation (SC24-5557-00) ° VM/Pass-Through Facility Programming Reference (SC24-5556-00).

1.0 Introduction



Virtual Machine/Pass-Through Facility, Version 2 (PVM), is a communications program that runs on the Virtual/Machine (VM) operating system (1). PVM has four components:

1. PASSTHRU (single session support for CMS users) 2. VM/Pass-Through Facility Multiple Session Application (MPVM) 3. VM/Pass-Through Facility Gateway (PVMG server) 4. VM/Pass-Through Facility Virtual Machine (PVM server).

(1) PVM Version 2 is supported on any of the following systems, at the stated release or service level or higher:VM/Enterprise System Architecture* (VM/ESA*) Release 1.1; VM/ESA Release 1.0 (ESA and 370 Feature);VM/SP Release 5; VM/SP HPO Release 5; VM/SP Release 6; VM/HPO Release 6; VM/Extended Architecture*(VM/XA*) System Product Release 2; VM/XA SP Release 2.1.

Subtopics:

1.1 Using the VM/Pass-Through Facility Version 21.2 What's New in this Version?1.3 Getting Online HELP

1.1 Using the VM/Pass-Through Facility Version 2

Using the VM/Pass-Through Facility, Version 2, lets you, as a general user:

° Establish interactive sessions with local and remote systems and applications (all components).

° Access the Systems Network Architecture (SNA) network from the PVM network (PVMG component).

° Access the PVM network from the SNA network (PVMG component).

° Save screen images on your local CMS minidisk when using PVM from a CMS virtual machine (PASSTHRU and MPVM components).

° Use the Escaped Command Facility to issue MPVM, CMS, or CP commands to your host CMS session while working with another local or remote session without disconnecting from your PVM session. Using this facility simply means you prefix CMS or CP commands with an escape character (MPVM component).

° Issue macros to improve efficiency in working with multiple applications (MPVM component).



° Issue general user PVM commands to obtain information from the VM/Pass-Through Facility servers (PVM and PVMG components).

° View online softcopy of this book and the following books:

- VM/Pass-Through Facility Administration and Operation - VM/Pass-Through Facility Programming Reference.

° Request online command and message help.

Administrators, operators, and programmers should see the VM/Pass-Through Facility Administration and Operation book for information about managing the network and the VM/Pass-Through Facility Programming Reference for information about writing MPVM macros and working with the multiple session environment.

1.2 What's New in this Version?

You can do more than access a single system. Now, the VM/Pass-Through Facility Version 2 provides:

° Multiple session support that lets you:

- Log on to several systems or applications while remaining logged on to your primary CMS system

- Send commands to your host CMS session using MPVM's Escaped Command Facility while remaining logged on to several systems or applications

- Create a nicknames file that lets you define nicknames and session characteristics through MPVM for working with systems

- Issue macros to improve efficiency in working with multiple applications in MPVM

- Save screen images using the MPVM NOTEPAD Facility.

° A gateway component that lets you:

- Access SNA applications from a PVM network

- Access remote systems and applications in a PVM network from an SNA network.



Think of PVM's Gateway component as a bridge between the two networks as shown in Figure 1:

Figure 1. You can access PVM and SNA networks using PVM's Gateway component. PVM users can access the SNA network by selecting an SNA application name from the PVM Selection Menu. SNA users can access the PVM network by specifying an application name for the PVMG component of PVM using the VTAM LOGON command.

In addition to these general user features, PVM Version 2 offers other features as listed in the VM/Pass-Through Facility Administration and Operation book.

1.3 Getting Online HELP

You can obtain online HELP for the following:

° General-use commands: CMD, CPQ, DIAL, MPVM, MSG, PASSTHRU, PMSG, QUERY, SHOW, and SMSG



See topic 2.1 if the PVM Initial Menu displays after powering on your workstation. If this menu displays, you already have access to PVM.

CP DIAL Command If your workstation screen displays the VM logon screen, you can access PVM without first logging on to VM. Move the cursor to the command line and enter the CP DIAL command. See topic 2.2 for information about accessing PVM from the command line of a VM logon screen.

VTAM LOGON Command See topic 2.3 for information about accessing PVM from the SNA network by specifying an application name for PVM's Gateway component (PVMG).

PASSTHRU Command See topic 2.4 for information about accessing PVM using the PASSTHRU command from within a CMS session and working with the PASSTHRU environment. This section also includes information about how to save screen images using the PASSTHRU NOTEPAD Facility.

PVM Selection Menu See topic 2.5 for information about establishing interactive sessions from this menu. This menu displays after accessing PVM in one of the following ways:

° Pressing CLEAR from the PVM Initial Menu ° Entering CP DIAL from the command line of a VM logon screen ° Entering the VTAM LOGON command specifying an application name for PVM's Gateway component (PVMG) ° Entering PASSTHRU from within CMS without specifying a node ID.

MPVM Command (Multiple Session Support) See topic 2.6 for information about establishing multiple sessions from within your primary host CMS session and working within the multiple session environment. This section also includes information about using MPVM commands and saving screen images using the MPVM NOTEPAD Facility.

Subtopics:

2.1 The PVM Initial Menu 2.2 The CP DIAL Command 2.3 The VTAM LOGON Command 2.4 The PASSTHRU Command 2.5 The PVM Selection Menu 2.6 The MPVM Command (Multiple Session Support)

2.1 The PVM Initial Menu If your workstation displays the following PVM Initial Menu, you already have access to PVM. (PVM is controlling your terminal rather than CP.)



__________________________________________________________________________________ | | | | | VM/Pass-Through Facility | | | | | | 1 Local Node RMTPVM1 | | 2 Address cuu cc pp | | | | Press ENTER for a session with the following options | | | | 3 Destination RMTPVM1 | | 4 End Session #### | | 5 Language AMENG | | 6 Verify OFF | | | | 7 Press CLEAR to view the selection screen | | | | 8 | | 9 | | PF1=RMTPVM1 PF2=VS1APL PF3=MVSTSO PF4=RMTPVM3 PF6=RMTPVM5 | | PF7=CHICAGO PF12=SYDNEY | | | | ****> 10 <**** | | ****> <**** | | | |__________________________________________________________________________________|

Figure 2. PVM Initial Menu

Use one of the following three ways to select a session:

1. Press ENTER to go to the system shown in the Destination field

2. Type over the name in the Destination field with another node ID and press ENTER

3. Press one of the PF keys for selecting a system assigned to a PF key.

Press the CLEAR key to display the PVM Selection Menu if you need to see a list of node IDs or need to change options that you cannot change on the Initial Menu.

Subtopics:

2.1.1 Initial Menu Explanations

2.1.1 Initial Menu Explanations



1 Local Node is the name of the PVM node controlling your workstation.

2 Address field indicates the address of your workstation:

° cuu indicates the real line address.

° cc and pp indicate cluster number and port number, respectively, if you are using a remote 3270 workstation.

3 Destination is your default target system or where you can enter a target system. This is the only field on the initial menu where you can type over information displayed in a field.

4 End Session #### displays the session terminate string (or PF or PA key) that you can use to end sessions if the usual logoff procedure for your target application does not return you to the Initial Menu.

5 Language tells you what language is in effect for your session; in this case, American English, AMENG.

6 General users should ensure the setting for this field is OFF. If it is ON, you will need to press the CLEAR key to view the selection menu where you can change the setting to OFF. If you are a system programmer, see the appendix on topic A.0 for information about I/O verification.

7 Press CLEAR to display the selection menu (shown in Figure 3 in topic 2.5) for a list of more system node IDs or to change options that you cannot change on the Initial Menu.

8 PVM messages display in this area.

9 The PF keys have been defined to represent a fast way to select a node ID.

10 The LOGMSG area displays messages from the operator.

2.2 The CP DIAL Command You can access PVM using the CP DIAL command from the command line of a VM logon screen. This might be useful if you are not at your primary location and a logon screen displays for which you do not have a user ID. Enter the CP DIAL command as follows:

| | | USERID ===>



| PASSWORD ===> | COMMAND ===> dial pvmid | |__________________________

where pvmid is the user ID of the virtual machine running PVM (usually the user ID is PVM). PVM responds to the DIAL command by displaying the selection menu as shown in Figure 3 in topic 2.5.

2.3 The VTAM LOGON Command From the SNA network, you can access the PVM network through PVM's Gateway component (PVMG). This component is defined in your SNA network as a VTAM application. Therefore, you must first use the VTAM LOGON command to access PVMG as follows:

LOGON APPLID(applname)

where applname is the application name by which VTAM knows PVMG. This takes you to a PVM Selection Menu as shown in Figure 3 in topic 2.5.

Note 1. Your installation might be using a special application that lets you select VTAM applications directly from a selection menu. If so, you can select the application name of the PVMG component directly from this menu rather than using the LOGON command.

Note 2. You might need to ask your administrator what the application name is for the PVM network.

You can bypass the PVM Selection Menu by specifying a PVM node name with the DATA option of the LOGON command:

LOGON APPLID(applname) DATA(NODE=nodeid)

where nodeid is a specific target system you want to access within the PVM network. If you specify more than one option, you must separate the options with a comma. For example, the following LOGON command will indicate that the language is Japanese (KANJI) and that pressing PF3 will terminate your PVM session:

LOGON APPLID(applname) DATA(LANG=kanji,SESSTERM=pf3)

Enter this command with no space between the option names and use closing parentheses as shown. Information provided with the DATA option is sometimes known as CINIT data.

The following DATA options are supported by PVMG:

NODE=nodeid



Specify a 1- to 8-character target system node ID you want to access within the PVM network.

ROUTE=nodeid Specify a 1- to 8-character system node ID through which you want PVM to route your session (2). Your session will then be routed from your local node to the secondary node and from the secondary node to your destination node. In this way, you can sometimes establish your session even when the usual path to your destination node is unavailable due to outages. Check with your PVM administrator to determine what secondary node you can specify as an alternate path to your destination node.

SESSTERM=string|key Specify a 1- to 8-character string or a PA or PF key. If entering LOGOFF from an application does not return you to the point where you first accessed PVM, use the session terminate function to do so. The default character string is set by your system administrator; you can view it on the selection menu as shown in Figure 3 in topic 2.5.

LANG=langid Specify a 1- to 5-character language identifier such as AMENG for American English or UCENG for Uppercase English.

PORT=nn Ordinarily, you will not need to specify a port address. However, if you are accessing a system through PVM's 327x control unit emulator, you might need to specify a port number to ensure that the system you are accessing recognizes your display unit type. If this is the case, check with your system administrator to find out what port numbers agree with your device type. The value specified for port must be a number in the range of 0 through 31.

IOV=ON|OFF General users should not use the input/output verification (IOV) option. The default setting is OFF. For more information about I/O verification, see the appendix on topic A.0.

(2) You can use the SHOW PATH command to determine the usual path from one node to another and use theQuery SYstem command to determine the names of other nodes that could be used for secondary routing. Usethe CMD command to direct any other command, such as SHOW or Query, to a PVM node other than your localnode. See topic 3.0 for examples of using the SHOW PATH, Query SYstem, and CMD commands.

2.4 The PASSTHRU Command This section covers:

° Working with the PASSTHRU command



° Switching between your host and target session ° Using the PASSTHRU NOTEPAD Facility.

If you have already logged on to a VM system and are using CMS, you can access PVM by entering:

passthru

which displays the PVM Selection Menu as shown in Figure 3 in topic 2.5.

Note: Entering PASSTHRU with no parameters uses a default PVM user ID of PVM. If the PVM server is using a PVM user ID other than PVM, this will not work; you must specify the PVM user ID that your system has defined by specifying a vmid as shown in Table 2 in topic 2.4.1.

You can bypass the PVM Selection Menu by entering the following from CMS:

passthru nodeid

where nodeid is the system you want to access. This takes you directly to that system's logon screen.

Subtopics:

2.4.1 Working with the PASSTHRU Command 2.4.2 Using the PASSTHRU NOTEPAD Facility

2.4.1 Working with the PASSTHRU Command

The following examples show how to specify PASSTHRU with parameters. For a frequently-used or complex PASSTHRU command, you can assign a PA or PF key to automatically issue the PASSTHRU command. You can also write a small exec for entering the command; this avoids having to remember all the parameters (this is explained later on topic 2.4.1.1.1).

passthru * * * * * * * * * * * 1 2 3 4 5 6 7 8 9 10 11 | | | | | | | | | | |langid | | | | | | | | | |YES | | | | | | | | |sec | | | | | | | |term | | | | | | |tdisc | | | | | |columns | | | | |lines | | | |notepf | | |vmid



2.4.1.1.2 Putting the PASSTHRU Command in a Small Exec 2.4.1.1.3 Creating Nicknames in Your CMS User ID NAMES File 2.4.1.1.4 Creating Synonyms in a CMS SYNONYM File

2.4.1.1.1 Switching Between Your Host and Target Session

Setting a PF or PA key or a 1- to 8-character string as the temporary disconnect function (TDISC) for the PASSTHRU command lets you switch from one session to the other without logging off from your PVM session as shown in the following sections:

Setting a PF or PA Key as the PASSTHRU Command for Your Current Session: By setting a PF or PA key on your host CMS session, you can execute the PASSTHRU command by pressing the PA or PF key you define rather than typing PASSTHRU each time you access another system. For example, to set PF1 to start a session with NEWYORK, you could enter:

cp set pf1 immed passthru newyork * * * * * back

Defining PF1 to issue the PASSTHRU command lets you press PF1 to start a session with NEWYORK and sets the temporary disconnect function (TDISC) to a character string of BACK. For details about the CP SET command, see the CP Command Reference.

Setting a PF or PA Key as the PASSTHRU Command in Your PROFILE EXEC: If you frequently access the same system, adding a CP SET command in your host system PROFILE EXEC can be helpful. For example, if your host system is RMTPVM1 and you frequently access RMTPVM2, you could first determine an available PF key by entering:

q pf

If PF2 does not already have a setting, you could put the following entry in your PROFILE EXEC:

CP SET PF2 IMMED PASSTHRU RMTPVM2 * * * * * PF2

After IPLing your host system, pressing the PF2 key invokes the PASSTHRU command and takes you to the RMTPVM2 system logo. After logging on to RMTPVM2, pressing PF2 returns you to your RMTPVM1 session and displays this message:

PVM is saving your session for you

Each time you press the specified PF key, this switches you from one session to the other.

2.4.1.1.2 Putting the PASSTHRU Command in a Small Exec



If you frequently specify the PASSTHRU command with parameters, you can write a small exec to invoke PASSTHRU automatically. For example, you could create a REXX exec called RMTPVM2 EXEC, containing the PASSTHRU command with parameters:

/************************************************************/ /* This exec automatically invokes the PASSTHRU command and */ /* sets the temporary disconnect function (TDISC) as PF2. */ /************************************************************/

address COMMAND 'EXEC PASSTHRU RMTPVM2 * * * * * PF2' exit

If you use a REXX exec as shown in this sample, the EXEC PASSTHRU portion of the command must be in upper case letters. Ensure that you add a REXX comment at the beginning of your exec and enclose the EXEC PASSTHRU instruction in quotes as shown. Now, you can execute the PASSTHRU command just by typing RMTPVM2 and pressing ENTER.

2.4.1.1.3 Creating Nicknames in Your CMS User ID NAMES File

You can name systems you access with a nickname by using your userid NAMES file. Within the userid NAMES file, you can use a :NODE. or :PVMNODE tag which PVM uses but other programs ignore. For example, the name HARTFORD could be a nickname for the system CONN1 and NYC could be a nickname for NEWYORK. You would need entries in your userid NAMES file that could look like these:

:nick.HARTFORD :node.CONN1 :nick.NYC :pvmnode.NEWYORK

After putting these entries in your userid NAMES file, you could request the CONN1 node by specifying HARTFORD or specify NYC rather than NEWYORK.

2.4.1.1.4 Creating Synonyms in a CMS SYNONYM File

To create a synonym called PASS for the PASSTHRU command, you would put the following entry in your synonym file:

PASSTHRU PASS

The word, PASS, is now a synonym for PASSTHRU; therefore, you can now enter PASS rather than PASSTHRU. For details about the CMS SYNONYM command, see the CMS Command Reference.



2.4.2 Using the PASSTHRU NOTEPAD Facility

Use the NOTEPAD function by defining a PF key number to invoke NOTEPAD when you specify the PASSTHRU command. Pressing the PF key you define as NOTEPAD copies a displayed screen image to a file on your host system file mode A. The default name of the NOTEPAD file is PASSTHRU DATA; it resides on file mode A. The following example illustrates using the PASSTHRU command with the NOTEPAD function. It is assumed that you are already logged on to the RMTPVM1 system and you have an inventory file of STOCK INVEN on the NEWYORK system.

1. Because you need some information from an inventory file on the VM NEWYORK system, enter:

passthru newyork * * 10 * * PF12

The asterisks denote default parameters (explained in Table 2 in topic 2.4.1). Specifying a number for the fourth parameter indicates you want a particular PF key number defined as NOTEPAD. Specifying asterisks in the fifth and sixth parameter position indicate you want to use the default number of rows and columns for saving screen images. The default number of lines is the number of lines on your display less the two lines at the bottom of your screen.

2. Log on to NEWYORK after the system logo appears. IPL CMS if it is not automatically done for you.

3. Edit the inventory file:

xedit stock inven

A file called STOCK INVEN displays:

| | | | | | | ===== * * * Top of File * * * | | |...+....1....+....2....+....3....+....4....+....5....+....6....+....7.... | | ===== 64400 GIZMO CC0101 9942 | | ===== 09263 WIDGET AA0403 8645 | | ===== 60637 THINGAMABOB BB0202 5432 | | ===== 26023 WHATCHAMACALLIT BB0306 9321 | | ===== * * * End of File * * * | | | | ====> | | X E D I T 1 File | | | |__________________________________________________________________________________|

4. Press PF10 to add the inventory information to your PASSTHRU DATA file on the RMTPVM1 system.



5. Enter:

quit

on the XEDIT command line to get out of the file.

6. Now, press the PF12 key to temporarily disconnect from NEWYORK. You are now back to RMTPVM1.

View the PASSTHRU DATA file; it contains the inventory information.

| | ===== 64400 GIZMO CC0101 9942 | ===== 09263 WIDGET AA0403 8645 | ===== 60637 THINGAMABOB BB0202 5432 | ===== 26023 WHATCHAMACALLIT BB0306 9321 | ===== * * * End of File * * * | | -------------------- | |_____________________________________________

The separator line at the bottom of the screen, --------------------, separates NOTEPAD screen images that PVM appends to your PASSTHRU DATA file. The last two lines of the screen image do not get appended to the PASSTHRU DATA file when the default screen size is used with NOTEPAD. This is why the XEDIT command line and the XEDIT status line are not in the PASSTHRU DATA file. Enter QUIT to get out of the file.

7. Enter the PASSTHRU command again:

passthru newyork * * 10 * * PF12

to return to your CMS session on NEWYORK and enter LOGOFF. PVM displays the following message:

Your session through PVM has ended

You are now back to your user ID on RMTPVM1. For information about copying specific parts of a screen image, see the lines and columns parameters in Table 2 in topic 2.4.1.

2.5 The PVM Selection Menu The PVM Selection Menu is displayed (as shown in Figure 3) if you:

° Press CLEAR while viewing the PVM Initial Menu (explained on topic 2.1) ° Enter the CP DIAL command on a VM logon screen (explained on topic



2.2) ° Enter the PASSTHRU command without specifying a node ID (explained on topic 2.4) ° Enter the VTAM LOGON command specifying an application name for PVMG (explained on topic 2.3).

__________________________________________________________________________________ | | | VM/Pass-Through Facility | | | | You can select a node with the cursor and press ENTER | | | | L RMTPVM1 G RMTPVM2 G RMTPVM5 S MVSTSO N RMTPVM3 R RMTSYS2 | | BOSTON CHICAGO ENDICOTT KATMANDU MASSENA OKFINOKI | | OTTOWA PAGOPAGO POTSDAM SHERWOOD SYDNEY TORONTO | | VMCMS VS1APL WATERLOO Z | | | | 1 | | | | 2 | | | | Destination --3---------------> Port ------------------------> 6 | | Route --------4---------------> Language --------------------> 7 AMENG | | End Session --5---------------> #### Verify ----------------------> 8 OFF | | Your Identification -------------------------------------------------> 9 SMITH | | 10 | | PF8= Scroll CLEAR key = Top Screen PA1= Exit | | PF1=RMTPVM1 PF2=VS1APL PF3=MVSTSO PF4=RMTPVM3 PF6=RMTPVM5 | | PF7=CHICAGO PF12=SYDNEY | | | | ****> 11 <**** | | ****> <**** | | | |__________________________________________________________________________________|

Figure 3. PVM Selection Menu

Use one of the following three ways to select a target application:

1. Place the cursor on a system name and press ENTER. 2. Type a node ID in the Destination field and press ENTER. 3. Press a PF key defined as a system node.

Subtopics:

2.5.1 Selection Menu Explanations

2.5.1 Selection Menu Explanations



1 This area displays a list of node IDs. You can press PF8 to display more node IDs (if any). The letters (L, N, S, R, G) that precede some of the node IDs indicate:

L Your local PVM system

N A PVM or PVMG node connected by a single communication line

S A non-PVM system (such as MVS) using PVM's 327x control unit emulator

R A node ID used by an operator for dialing a remote 4300 processor using the Remote Operations Communications Facility (ROCF)

G A PVM node that is connected by a group of communication lines.

Note: Node IDs with one of these letters: N, S, R, or G indicate a direct link to an adjacent node. The remaining node IDs (without a preceding letter) are in alphabetical order and are accessed indirectly through adjacent PVM nodes.

2 Error and informational messages display in this area.

3 Destination is where you enter the 1- to 8-character name of the system or application with which you want to start a session.

4 Route is a 1- to 8-character system node ID through which you want PVM to route your session (4). Your session will then be routed from your local node to the secondary node and from the secondary note to your destination node. In this way, you can sometimes establish your session even when the usual path to your destination node is unavailable. If a network link is down, ask your PVM administrator what you can specify in this field as an alternate route.

5 End Session displays a session terminate string or a PA or PF key for ending sessions. You can change this field by typing over the displayed string characters with a 1- to 8-character string or a PA or PF key in the form, PFnn or PAn. Entering this character string (or pressing the assigned PA or PF key) ends the session you are using. For example, if entering LOGOFF from an application does not return you to the point where you first accessed PVM, use the session terminate function to do so. The default character string or key is set by the system administrator and is displayed in this field.

6 Ordinarily, you will not need to specify a port address. However, if you are accessing a system through PVM's 327x control unit emulator, you might need to specify a port number to ensure that the system you are accessing recognizes your display unit type. If this is the case, check with your system administrator to find out what port numbers agree with your device type. The value specified must be a number 0 through 31.

7 Language displays the language that is in effect for your session.



You can change the language by typing over what is displayed in this field with the identifier of another available language. Using the SMSG PVM Q LANG command will display available languages for your system. Languages that might be included on your system are Japanese (KANJI), Uppercase English (UCENG), and American English (AMENG).

8 General users should ensure that this field indicates OFF. See the appendix on topic A.0 for more information about I/O verification and the use of this field.

9 Your Identification identifies your session as follows:

° Your user ID if you started the session with the PASSTHRU command

° Your display virtual device address, in the format GRAFnnn or GRAFnnnn, if the session is started with the CP DIAL command

° CLxx-Pyy, where xx is the cluster address and yy is the port address for sessions started from remote 3270 devices

° The real address of the device for directly-connected terminals (a 1- to 8-character string)

° The SNA logical unit (LU) name for sessions from VTAM (a 1- to 8-character string).

Note: You cannot change this field.

10 Press PF8 to scroll the screen forward to display more node IDs.

Press CLEAR to return to the top of the list.

Press PA1 to return to where you started. For example, if you got to this menu from the Initial Menu, pressing PA1 takes you back to the Initial Menu, or if this menu displayed after you entered PASSTHRU from within a CMS session, you return to that particular CMS session.

Other PF keys are displayed if your PVM administrator has assigned them to certain node IDs.

11 The LOGMSG area displays messages from the operator.




2.6 The MPVM Command (Multiple SessionSupport) This section provides information about accessing multiple systems or applications using PVM's multiple session support (MPVM component) as follows:

° Using the MPVM Selection Menu ° Working with the MPVM command ° Using the MPVM command with the Escaped Command Facility ° Switching among multiple active sessions ° Using MPVM's NOTEPAD Facility ° Setting PA, PF keys, or SysReq key ° Creating a personal MPVM NAMES file ° Changing variable settings ° Issuing MPVM commands.

The end of this section shows examples of multiple session activities.

Subtopics:

2.6.1 Using the MPVM Selection Menu 2.6.2 Working with the MPVM Command 2.6.3 Switching Among Multiple Active Sessions 2.6.4 Using the MPVM NOTEPAD Facility 2.6.5 Creating a Personal MPVM NAMES File 2.6.6 Setting PA, PF Keys, or SysReq Key 2.6.7 Changing Variable Settings 2.6.8 Issuing MPVM Commands 2.6.9 Example: Multiple Session Activities

2.6.1 Using the MPVM Selection Menu

To access MPVM you must have a user ID on the system where the MPVM code resides; this is your host session (5). After logging on to your local VM system (host CMS session) and IPLing CMS, you can access multiple session support by entering:

mpvm

The MPVM Selection Menu displays.

__________________________________________________________________________________ | | | | | VM/Pass-Through Facility |



| 1 | | You can select a session with the cursor and press ENTER | | _____________________________________________________________________________ | | | | | | 2 | | CHICAGO CUSTDB DENVER LIBRARY LONDON NEWYORK PAYROLL | | SALES TOKYO TOLEDO TORONTO VM1 VM2 VM3 | | | | | | | | | | | | 3 | | | | _____________________________________________________________________________ | | 4 | | PF3=Return PF6=Disconnect | | PF7=Backward PF8=Forward PF9=Retrieve | | PF10=Top PF11=Bottom PF12=EXIT | | | | ====> Û 5 | | | |__________________________________________________________________________________|

Figure 4. MPVM Selection Menu

Do one of the following to select a session:

1. Place the cursor under a nickname and press ENTER. 2. Type a nickname on the selection menu's command line and press ENTER. 3. Press PF8 to display more nicknames (if any).

(5) This book refers to a session as an application or system that is accessed.

Subtopics:

2.6.1.1 Selection Menu Explanations

2.6.1.1 Selection Menu Explanations

The Û at the input area (command line) indicates the cursor.

1 A nickname is a session name defined in an MPVM names file (6).

2 Sessions are shown in alphabetical order. Later, after you have



accessed sessions, they are shown in the order you accessed them.

3 This area displays messages.

4 The following explains the PF keys defined on the menu other than the keys that move data on the screen backward, forward, to the top, or to the bottom of the screen (PF7, PF8, PF10, PF11 respectively).

PF3 Returns you to the last session you accessed or your host CMS system if none are accessed.

PF6 Temporarily disconnects you from MPVM and returns you to your host CMS session.

PF9 Recalls the last five commands (one at a time) that you entered from the command line of this menu.

PF12 MPVM prompts you by asking if you really want to terminate all sessions. By pressing PF12 again, all sessions terminate and you return to your host session.

5 The ====> at the bottom left corner of the screen indicates an input area (command line) where you may enter a session name that is displayed on the menu or a command that you want executed at your host CMS session. See topic 2.6.3.1 for more information about working with your host CMS session.

(6) MPVM names refer to the MPVMSYS NAMES file or a personal MPVM NAMES file and contains thedefinitions that describe each nickname entry.

2.6.2 Working with the MPVM Command

Use the MPVM command from within your host CMS session to access multiple session support by entering:

mpvm

which displays the selection menu as shown in Figure 4 in topic 2.6.1.

Subtopics:

2.6.2.1 Specifying Parameters with the MPVM Command



2.6.2.2 Using the MPVM Command with the Escaped Command Facility

2.6.2.1 Specifying Parameters with the MPVM Command

The following are basic parameters you can specify with the MPVM command for establishing multiple sessions:

mpvm langid nickname pvmid

All parameters are optional. If you specify a nickname from within your host CMS session and do not specify a langid, you must specify an asterisk as a placeholder. Additional parameters are described in online HELP and in the VM/Pass-Through Facility Programming Reference.

langid is a 1- to 5-character language ID that is used to display system responses.

nickname is a name that is defined in the MPVMSYS NAMES file or in your own personal MPVM NAMES file. Specifying a nickname takes you directly to the logon screen for the specified nickname. If you do not specify a langid, you must specify an asterisk as a placeholder, like this:

mpvm * nickname

This takes you directly to the logon screen of the target system associated with the nickname.

pvmid is the user ID of the PVM server you want to connect to. Ordinarily, you do not need to specify this parameter. Remember, you must specify an asterisk if you do not specify a langid or a nickname. See the VM/Pass-Through Facility Programming Reference for more complete MPVM command reference information.

2.6.2.2 Using the MPVM Command with the Escaped Command Facility

After you have accessed MPVM, you must precede the MPVM command with an escape character prefix when you are not within your host session. For example, from a session other than your host CMS session, enter the MPVM command like this:

?mpvm

to display the MPVM Selection Menu (7). From outside your host system, entering:



?mpvm nickname

bypasses the selection menu and takes you directly to the logon screen of the target system associated with the nickname.

Note: After you have accessed MPVM initially from your host system, specifying langid (or an asterisk) before specifying a nickname does not apply. See online HELP or the VM/Pass-Through Facility Programming Reference for additional operands for issuing MPVM.

Starting additional sessions with other systems or applications is similar to starting your initial session except you must use the escape character prefix when you are not using your CMS host session.

1. Enter:

?mpvm

to display the MPVM Selection Menu.

2. Select an application or session nickname from the displayed selection menu.

Note: An administrator defines a maximum allowable number of sessions per user for the MPVM environment. Whatever session is currently being displayed at your workstation is your current session.

3. Log on to the displayed system logo.

(7) PVM's default escape character prefix is a question mark. Your system may have set a different escapecharacter prefix. See your administrator if using the question mark does not work.

2.6.3 Switching Among Multiple Active Sessions

This section shows you how to switch among multiple sessions, work with your host CMS session, and get information about sessions.

After starting several sessions, you can switch among active sessions using the SELECT command. This book refers to a target application or system as a destination you want to reach.

Suppose you have established sessions using nicknames, LIBRARY, PAYROLL,



and SALES and you are currently working with SALES. To switch control to the LIBRARY session, enter:

?select library

You can also use the SELECT command without specifying a session's nickname. For example, if you started the three sessions in this order:

LIBRARY PAYROLL SALES

SALES is your current session. If you entered:

?select

PAYROLL becomes your current session. The SELECT command "wraps around" when you enter it from your initial MPVM session. Using the same example sessions, entering the SELECT command when LIBRARY is the current session, the new current session becomes SALES. In addition to specifying SELECT from the command line, you can define a PA, PF, or SysReq key as SELECT to switch from one session to the next. Selecting sessions with the SELECT command works in a wraparound fashion. You can select or switch in succession from one session to the next.

Subtopics:

2.6.3.1 Working with Your Host CMS Session 2.6.3.2 Using the WHERE Macro to Get Information about Sessions

2.6.3.1 Working with Your Host CMS Session

While working with multiple sessions, you can work with your host CMS session by simply preceding a CMS, CP, or an MPVM command with an escape character prefix. For example, entering the following command from any session (other than your host CMS session) or from the command line of the MPVM Selection Menu:

?xedit profile exec

displays the PROFILE EXEC A on your host CMS session.

2.6.3.2 Using the WHERE Macro to Get Information about Sessions

To get information about which session you are currently using and about



sessions that are active, use the WHERE macro. From within a session, specify WHERE prefixed with the escape character:

?where

which displays the nickname of your current session, as well as any other active sessions you may have similar to this:

Current session: PAYROLL Other sessions... SALES LIBRARY

2.6.4 Using the MPVM NOTEPAD Facility

Use NOTEPAD in the MPVM environment (other than your host session) to save screen images in one of the following ways:

° Issue the NOTEPAD command with an escape character prefix

° Set a PF key as the NOTEPAD command.

From within a session other than your host session, enter:

?notepad

and the entire screen image automatically goes into a file called fn MPVMDATA on file mode A of your host system. The file name of this file is the nickname of the session, unless your system has defined it differently.

You can save a partial screen image for displayed data by specifying starting and ending screen row positions. Entering:

?notepad 7 14

saves rows 7 through 14 of the displayed screen data.

Subtopics:

2.6.4.1 Setting a PF Key as NOTEPAD 2.6.4.2 Setting Up Separate NOTEPAD Files

2.6.4.1 Setting a PF Key as NOTEPAD



Use the MPVM SET command to set a PF key as NOTEPAD while you are using a session:

?set pfnn notepad

The PF key setting will be in effect while you are logged on to that session. You must put an entry in your personal MPVM NAMES file to set NOTEPAD for all sessions.

Warning: PF or PA keys you define in MPVM take precedence over keys already set in applications you may be using. For example, if PF3 is set as QUIT for your XEDIT sessions and you set PF3 as NOTEPAD through MPVM, the NOTEPAD function will execute when you press PF3. See page 2.6.9 for an example of putting a NOTEPAD entry in a personal MPVM NAMES file.

2.6.4.2 Setting Up Separate NOTEPAD Files

To set up more than the one default NOTEPAD file, define NOTEPAD file names in a personal MPVM NAMES file. See "Example: Multiple Session Activities" in topic 2.6.9 for information on how to do this.

2.6.5 Creating a Personal MPVM NAMES File

Your system has an MPVMSYS NAMES file (owned by the PVM administrator) that defines information such as:

° System node IDs ° Nicknames ° Characteristics of sessions ° NOTEPAD file names ° PA, PF, and SYSREQ key definitions.

You can tailor session characteristics by creating your own personal version of this file. You must name it MPVM NAMES and keep it on file mode A of your host CMS system. You put :nick. tags and subtags in the MPVM NAMES file to define nicknames and characteristics of systems and applications. Valid characters for specifying nicknames are:

a-z, A-Z, 0-9 # (number sign) & (ampersand) % (percent) @ (at sign) . (period) : (colon) ? (question mark) , (comma) _ (underscore)

Note: Nicknames must be unique to all currently established sessions. Do



not use the word CANCEL or start a nickname with an escape character (default value ?).

Every nickname you put in this file must have a :nick. and a :target. tag. Each session nickname, :nick.value, can have other tags associated with it called subtags that provide more information. A :nick. tag and its subtags constitute a NAMES file entry and are structured within an MPVM NAMES file as follows:

Format Sample Entries

:nick.value :nick.VM1 :subtag1.value :target.gdlvm1 :subtag2.value :pf10.notepad

Note: Subtag names and values are indented for better readability.

Entries you put in your personal MPVM NAMES file override duplicate entries in the MPVMSYS NAMES system file. The nicknames you define in your MPVM NAMES file will be listed on the MPVM Selection Menu before nicknames from the MPVMSYS NAMES file.

Subtopics:

2.6.5.1 Other :Nick. Tags

2.6.5.1 Other :Nick. Tags

In addition to specifying a :nick. tag for a session nickname, there are two other uses for this tag:

:nick.?INITIAL Specifies values for MPVM in general when you enter the MPVM command. Subtags under this special :nick. tag are where you enter all global variable settings. You must specify a PA key or the SysReq key when using the :nick.?INITIAL tag. For example, putting this entry in your personal MPVM NAMES file:

:nick.?INITIAL :PA1.SELECT

sets PA1 key function as the SELECT command for all sessions. A global variable setting is one that is in effect for all sessions. For example, assigning PA1 to SELECT will be in effect for all sessions. A local variable setting is one that is in effect for your current session only. For example, assigning PF1 to ?WHERE will be in effect only for the current session.

:nick.?DEFAULT



2.6.7 Changing Variable Settings

Some of the settings you can change from within your current session are:

ALARM ON sounds the system's alarm when certain events take place. To set the alarm off, enter:

?set alarm off

BEEPZero ON is the initial setting; you can change the BEEPZero value to OFF. While you are using a session, enter:

?set beepz off

This command changes the workstation beep sound to OFF rather than having the system beep each time you get a return code zero from an escape command your host session processed.

To automatically set values, you can put subtag entries in your personal MPVM NAMES file.

You can display the value of most MPVM variables using the QUERY command. See topic 2.6.8.1 for examples.

2.6.8 Issuing MPVM Commands

The following section describes general user MPVM commands you can issue in the multiple session environment. Remember, when you issue MPVM commands from outside your host system, you must prefix an MPVM command with an escape character. Prefix any CMS, CP, or MPVM command with an escape character when you want to issue a command to the host session. The default is a question mark; however, the escape character can be changed to any one-character symbol. For example, from outside your host session entering:

?set escape symbol

changes the escape character setting for all sessions. This setting stays in effect until you exit from MPVM. To have the escape character prefix of your choice in effect each time you invoke MPVM, add an entry to your personal MPVM NAMES file.



2.6.9.1 Putting Entries in a Personal MPVM NAMES File

This example begins with Pat Smith putting the following entries in a personal MPVM NAMES file on file mode A of the host system:

:nick.?default :pa1.select :pf12.notepad :nick.custdb :target.denver :npfn.denver

Figure 5. Pat Smith's MPVM NAMES File Entries

PA1 has been set as the SELECT command. PF12 has been set as NOTEPAD. Specifying a PA or PF key subtag under the :nick. ?DEFAULT tag indicates defining that key will be in effect for all sessions defined in the MPVM names files. The :npfn. tag defines a NOTEPAD file name, DENVER. The file type will be PVM's default of MPVMDATA. See "Using the MPVM NOTEPAD Facility" in topic 2.6.4 or Table 4 in topic 2.6.8 if you need more information.

2.6.9.2 Displaying Multiple Sessions

The following display sequences show how Pat Smith at the New York location (NEWYORK host CMS system) uses PVM's multiple session support (MPVM). Let's follow Pat through some sample MPVM sessions.

___ ___________________________ ________________________________________

| 1 | | Pat's terminal displays the NEWYORK | | | | system logo. (NEWYORK is the host | | | | system, where MPVM resides.) | |___|___________________________|________________________________________|



|___|___________________________|________________________________________|

| 2 | | Pat logs on to the host session (using | | | | the SMITH user ID) and next, enters | | | | the MPVM command. | |___|___________________________|________________________________________| |___|___________________________|________________________________________|

| 3 | | The MPVM Selection Menu displays. The | | | | CUSTDB session nickname is defined in | | | | Pat's MPVM NAMES file and is listed | | | | along with other sessions defined in | | | | the system-wide MPVMSYS NAMES file | | | | (like LIBRARY, PAYROLL and SALES). | | | | | | | | Pat selects the session nicknamed | | | | LIBRARY which now becomes the current | | | | session. | |___|___________________________|________________________________________| |___|___________________________|________________________________________|

| 4 | | The LIBRARY application is on the | | | | NEWYORK system (the same system as | | | | Pat's host session). The NEWYORK logo | | | | is displayed again. | |___|___________________________|________________________________________| |___|___________________________|________________________________________|

| 5 | | Pat logs on to the LIBRARY application | | | | with a user ID for that application | | | | (in this case, LIBRARY). | | | | | | | | After logging on to LIBRARY, Pat | | | | starts a second session, nicknamed | | | | CUSTDB by using the escape character | | | | to send the MPVM command to the host | | | | system. (Remember, when specifying | | | | MPVM with an escape character, an | | | | asterisk is not required before | | | | specifying a nickname.) | |___|___________________________|________________________________________| |___|___________________________|________________________________________|



|___|___________________________|________________________________________| |___|___________________________|________________________________________|

| 9 | | MPVM redisplays the current session, | | | | LIBRARY. After doing a little more | | | | work on LIBRARY, Pat enters the LOGOFF | | | | command, ending the session. | |___|___________________________|________________________________________| |___|___________________________|________________________________________|

| 10| | MPVM displays a message on Pat's host | | | | session indicating that the LIBRARY | | | | session has ended. | |___|___________________________|________________________________________| |___|___________________________|________________________________________|

| 11| | MPVM displays the selection menu. The | | | | CUSTDB nickname is highlighted, | | | | indicating that the session is still | | | | active. Pat presses the PF3 key to | | | | return to CUSTDB. | |___|___________________________|________________________________________| |___|___________________________|________________________________________|

| 12| | Pat enters the LOGOFF command on | | | | CUSTDB, ending that session. | |___|___________________________|________________________________________| |___|___________________________|________________________________________|

| 13| | Again, MPVM displays a message on | | | | Pat's host session indicating that the | | | | CUSTDB session has ended. | |___|___________________________|________________________________________| |___|___________________________|________________________________________|



| 14| | MPVM displays the selection menu. No | | | | nicknames are highlighted. Pat has | | | | finished working with MPVM for now and | | | | presses PF12 to exit from the | | | | selection menu. | |___|___________________________|________________________________________| |___|___________________________|________________________________________|

| 15| | MPVM returns control of Pat's virtual | | | | machine to the host user ID on CMS. | |___|___________________________|________________________________________| |___|___________________________|________________________________________|

3.0 Part 2: Issuing PVM Server Commands As a VM user, you can issue certain commands to any PVM or PVMG server in a PVM network. The commands you can issue, as a general user, are shown in the following table:

________________________________________________________________________ | Table 5. General User PVM Server Commands | |______________________ _________________________________________________| | Command | Description | |______________________|_________________________________________________| | CMD | Sends PVM commands to another PVM node ID. | |______________________|_________________________________________________| | CPQ | Issues one out of a specific set of CP commands | | | on a remote system. CPQ is supported only by | | | the PVM component. | |______________________|_________________________________________________| | MSG | Sends a message to a local or remote VM user | | | ID. | |______________________|_________________________________________________| | PMSG | Sends a message to a specific PVM user's | | | workstation. | |______________________|_________________________________________________| | Query | Displays information about network status, | | | devices, and session information. | |______________________|_________________________________________________| | SHOW | Displays the origin or destination of a PVM | | | session you specify, or displays the path to a | | | node ID you specify. | |______________________|_________________________________________________|



This section shows how to issue PVM server commands and provides examples of using PVM commands to:

° Request information about network links ° Request information about sessions ° Request information about installed languages ° Request routing information ° Send a message to a remote VM user ° Send a message to a local or remote PVM user's workstation.

It is suggested that you try the examples used in this section on your own system, using node names available in your own PVM network, and experiment with these commands to determine how they might be useful to you.

Subtopics:

3.1 The CP SMSG Command 3.2 Issuing a Command to a Remote PVM or PVMG Node 3.3 Specifying a Language For Command Responses 3.4 The SHOW Command 3.5 The Query Command 3.6 The MSG and PMSG Commands 3.7 The CPQ Command 3.8 More Information on PVM and PVMG Server Commands

3.1 The CP SMSG Command

The CP Special Message (SMsg) command is used to forward a command to another virtual machine for processing by a program running in that virtual machine. To issue a PVM server command, use the CP SMsg command to send the PVM command to a virtual machine running PVM or PVMG on your local system, as follows:

CP SMSG pvmid pvmcmd

where pvmid is the user ID of a virtual machine running PVM or PVMG and pvmcmd is a PVM command.

3.2 Issuing a Command to a Remote PVM or PVMG Node

Use the CMD command to forward another PVM command to a remote PVM node for command processing, as follows:

CP SMSG pvmid CMD nodeid pvmcmd

where nodeid is the node name of the PVM you want to process the command.



Your local PVM will forward the command to the nodeid through the PVM network, and the PVM program at the nodeid will process the command and send any command responses to you.

3.3 Specifying a Language For Command Responses

You can use the (L.langid) command prefix to tell PVM to use a particular language when responding to your command, as follows:

CP SMSG pvmid (L.langid) pvmcmd

where langid is the 1- to 5-character language identifier of a language installed on PVM at the site where you enter the command. If you use the prefix when sending a command to a remote PVM, place the prefix in front of the CMD command, as follows:

CP SMSG pvmid (L.langid) CMD nodeid pvmcmd

To find out what languages are available at your local PVM site, use the Query LANGs command, as follows:

CP SMSG pvmid Q LANG

If you usually work in the United Kingdom and were planning a trip to Japan, you might want to know ahead of time whether your language is installed on the PVM node called TOKYO, particularly if you would be using PVM while in Japan to access your system back in the United Kingdom. You could find this out by entering:

CP SMSG pvmid CMD TOKYO Q LANG

If your language were not installed, you could request that it be installed before leaving on your trip. While in Japan, you could then select your own language for interactive sessions through PVM, and could use the (L.langid) prefix to specify your own language for command responses when entering PVM commands.

3.4 The SHOW Command

To determine what PVM nodes are included in the path to a particular system you need to access through PVM, use the SHOW command with the PATH option. For example, you could use the following command to determine the path to the node called TOKYO:

CP SMSG pvmid SHOW PATH TOKYO

If the node name of your local PVM were KINGDOM, you could find out the



path from TOKYO to KINGDOM, which might be different than the path from KINGDOM to TOKYO, as follows:

CP SMSG pvmid CMD TOKYO SHOW PATH KINGDOM

3.5 The Query Command

The Query command has many options. You can obtain information about network links connected to a PVM node by using the SYstem option, as follows:

CP SMSG pvmid Q SYS

By using combinations of the CMD, SHOW PATH, and Query SYstem commands, you can get a good picture of the topography of your PVM network. And this can be helpful if you need to specify an alternate route to a destination node for an interactive session when the usual path to the destination node is unavailable due to outages.

Use the SYstem Queue option of the Query command to obtain information about sessions, in addition to information about network links, as follows:

CP SMSG pvmid Q SYS Q

A typical message issued in response to Query SYstem Queue might look like the following:

CHICAGO SMITH Device 1C18 3278 Model 4 HC is in session at NEWYORK L000, Bytes In 17504 Out 857

which indicates that user SMITH (8) at node CHICAGO is in a session using logical device L000 at node NEWYORK. SMITH is using a 3278 model 4 workstation with highlighting and color features (HC) located at real device address 1C18. Since SMITH started the session, 17504 characters have been transmitted from CHICAGO to NEWYORK for SMITH's session, and 857 characters have been transmitted from NEWYORK to CHICAGO.

You could obtain the same information about this particular PVM session by using the Query User command in either of the following forms:

CP SMSG pvmid Q U CHICAGO SMITH

CP SMSG pvmid Q U NEWYORK L000

If you specify an MPVM user's local node and host user ID as options to the Query User command, and direct the command to the user's local PVM node, the number of sessions for that user and information about each session will be displayed. A session identifier, *SESnnnn, displays for each MPVM session.



(8) The identifier, SMITH, would appear on this user's PVM Selection Menu in the Identification field.

3.6 The MSG and PMSG Commands

If SMITH, in the previous example, is logged on a VM user ID at NEWYORK, and you know the name of the user ID, you can send a message to SMITH's user ID at NEWYORK using the MSG command, as follows:

CP SMSG pvmid MSG NEWYORK userid What time are you going to lunch?

where userid is the name of SMITH's user ID at NEWYORK. PVM delivers your MSG message by passing it through the PVM network to the PVM node called NEWYORK, where it is issued to the indicated user ID using the CP MSG or MSGNOH command, whichever PVM at NEWYORK is using.

Note: The target user ID of the MSG command does not need to be associated with a PVM session.

The MSG command, however, will not work in the following cases:

° You do not know the user ID to which SMITH is logged on at NEWYORK.

° SMITH is not logged on a VM system. For example, NEWYORK might be an SNA application outside the PVM network.

° SMITH is logged on a VM system but has used SET MSG OFF and is not receiving messages.

If any of these cases applies, you can still send your message to user SMITH using the PMSG command, as follows:

CP SMSG pvmid PMSG CHICAGO SMITH What time are you going to lunch?

PVM delivers your PMSG message by interrupting the user's PVM session to display your message at the user's workstation.

Note: Any command issued from your console is converted to uppercase before it is passed on to PVM. By writing a small exec, similar to the TELL EXEC distributed with CMS, you can have your PVM MSG and PMSG command messages delivered in the form in which you type them.

3.7 The CPQ Command



You can use the CPQ command to issue a limited number of CP commands on a remote system. PVM will reflect any CP responses to you. For example, you can use the CPQ User command to find out whether a particular user is logged on, as follows:

CP SMSG pvmid CMD nodeid CPQ U userid

where nodeid is the node ID of a remote VM system and userid is a particular VM user ID.

To display detailed information about your host processor, specify the CPU option with the CPQ command as follows:

SMSG pvmid CPQ CPU

3.8 More Information on PVM and PVMG Server Commands

For a complete description of all PVM and PVMG commands and their associated options, see the VM/Pass-Through Facility Administration and Operation book.

4.0 Part 3: Appendix, Glossary, Bibliography andIndex This section of the book contains:

° An appendix for any PVM user interested in finding out more about recovering from a program error or requesting I/O verification

° A glossary that defines terms mentioned in this book and related terms

° A bibliography that lists helpful publications and tells you how to order the PVM library

° An index to assist you in retrieving information.

A.0 Appendix. Recovering from a Program Error This appendix gives you information about:



° What to do if PVM's Program Error Recovery screen displays ° What caused the screen to be displayed ° How to prevent the error in the future ° Requesting I/O verification.

After you select a system or application through PVM, PVM acts as a conduit between the system you selected and your workstation. Whenever the program writes something, PVM passes the data through the network and displays it on your screen. The device responds by indicating whether the write was successful. PVM can send this device status back to the program, but only if the program asked for it.

If an I/O error occurs and the program you are using has not requested device status, PVM is in a position from which it cannot recover on your behalf. The system you are using thinks the write was successful and is probably waiting for keyboard input from you.

Rather than just terminating your session when this situation occurs, PVM displays the following screen: (9)

__________________________________________________________________________________ | | | | | | | PROGRAM ERROR RECOVERY | | | | | | The program you are using through PVM has transmitted | | control information that is not compatible with your | | display unit. At this time you can attempt to recover | | from the error by pressing keys that are appropriate | | to the program you are using, or you can end your | | PVM session. The ENTER key will end your PVM session, | | unless you specified a PF or PA key for that purpose. | | | | | | | | | | | | | | | | | | | | End Session #### | | | | | | | |__________________________________________________________________________________|

Figure 6. Program Error Recovery Screen



(9) MPVM does not support the Program Error Recovery screen or I/O verification.

Subtopics:

A.1 Screen ExplanationsA.2 Preventing ErrorsA.3 Requesting I/O Verification

A.1 Screen Explanations

You can take any of the following three actions when this screen displays:

1. Terminate your PVM session using your session terminate string (or key).

Notice that your session terminate string (or key) is displayed at the bottom of the screen. If you press the ENTER key without doing anything else, it will have the same effect as typing this string in this field and pressing ENTER, which will terminate your session if a string (not a key) was in effect for session termination.

If you are using a PF or PA key for session termination, however, pressing ENTER will not terminate your session. In this case you must press the assigned PF or PA key to terminate your session.

2. Type over an area on the screen and press ENTER.

You can erase and type over most areas on the Program Error Recovery Screen. When you press the ENTER key after typing over a field, PVM passes this information to the program you were using. For example, you could type LOGOFF on an appropriate line of the screen, and it might result in a normal logoff from the system you were using.

Remember, however, that the 8-character field where your session terminate string (or key) is displayed will also be passed back to the program when you press ENTER. Erasing this field might be appropriate for your purpose.

3. Press a PF or PA key not assigned to terminate your session.

When you press a key not assigned to terminate your session, PVM passes this information to the program you were using. Even if the Program Error Recovery Screen re-appears after you press the key, due to a subsequent write error, the key will have had an effect if it had meaning to the program you were using. For example, pressing PF3 could get you out of an XEDIT session if PF3 were assigned to QQUIT.



And this might be better than terminating your PVM session without first getting out of your XEDIT session.

A.2 Preventing Errors

The best way to handle I/O errors of this kind is to understand what causes them and take appropriate actions to prevent them.

3270 I/O errors usually occur because the system you are using through PVM thinks you are using a particular type of workstation when you are actually using another. The most common cause is dialing a second-level operating system without specifying a virtual address on the CP DIAL command.

For example, assume you select a VM system through PVM; a VM logon screen appears. Instead of logging on, you space down to the command line and DIAL a virtual machine running MVS without specifying a virtual address. In this case, CP assigns the virtual machine's first available GRAF address to your session. If the VTAM subsystem running in the second-level MVS system thinks the device attached to that address is a different type of workstation than the one you are actually using, an I/O error might result when VTAM writes data to your screen.

Whenever you are using a second-level system, such as MVS, through PVM, you should find out from your system administrator which virtual GRAF addresses are generated in the second-level operating system as the type of workstation you are actually using. Then specify one of those virtual GRAF addresses on the CP DIAL command when you DIAL the virtual machine. See the CP Command Reference for more information about specifying a virtual GRAF address with the CP DIAL command.

A.3 Requesting I/O Verification

When starting a session through PVM, you can request that your target system do its own I/O verification. Do this in one of the following ways:

° Type ON in the Verify field of the PVM Selection Menu as shown on topic 2.5.

° Specify YES as the tenth parameter on the PASSTHRU command as shown on topic 2.4.1.

° Specify IOV=ON in the DATA field of the VTAM LOGON command as explained on topic 2.3.

Requesting that your target system do its own I/O verification does not guarantee the target system will do it; not all applications have this capability. However, if your target system is accessed by PVM through the CP Logical Device Support Facility, PVM will inform CP of your request.



To do its own I/O verification, your target application requests I/O status each time it writes something to your workstation. This can result in significant performance degradation, because the application will do nothing else until it receives the device status back from PVM for the last individual write. The amount of performance degradation varies with the distance between your workstation and target application in the network.

Unless you are a system programmer testing a system application that writes its own 3270 data streams, it is recommended that you ensure I/O verification is OFF whenever you begin a session through PVM.

GLOSSARY Glossary

C

CMS. Conversational Monitor System.

command. A request from a user at a terminal for the execution of a particular CP, CMS, IPCS, GCS, TSAF, orAVS function. A CMS command can also be the name of a CMS file with a file type of EXEC or MODULE.

command line. The line at the bottom of display panels that lets a user enter commands or panel selections. It isprefixed by an arrow (====>).

component. A collection of elements that together form a separate functional unit. A product may contain manycomponents. For example, PVMG is a component of PVM.

connect. Establishing a path to communicate with another virtual machine or with the user's own virtualmachine.

console. A device used for communications between the operator or maintenance engineer and the computer.

Control Program (CP). A component of VM that manages the resources of a single computer so multiplecomputing systems appear to exist. Each virtual machine is the functional equivalent of an IBM System/370*.

CP command. A command available to all VM users. Class G CP commands let the general user reconfiguretheir virtual machine, control devices attached to their virtual machine, do input and output spooling functions,and simulate many other functions of a real computer console. Other CP commands let system operators, systemprogrammers, system analysts, and service representatives manage the resources of the system.



D

destination. Is your default target system or application as displayed on the PVM Initial Menu or the PVMSelection Menu in the Destination field.

disk. A magnetic disk unit in the user's CMS virtual machine configuration. Also called a virtual disk.

display device. An I/O device that gives a visual representation of data.

E

edit. A function that makes changes, additions, or deletions to a file on a disk. These changes are interactivelymade. The edit function also generates information in a file that did not previously exist.

escape character. The character used to signal PVM that the following string is an escaped command, to beprocessed on the user's host ID. The initial escape character setting is ?, but it may be tailored.

F

file mode. A two-character CMS file identifier field containing the file mode letter (A through Z) followed bythe file mode number (0 through 6). The file mode letter indicates the minidisk or SFS directory on which thefile resides. The file mode number indicates the access mode of the file. See file access mode.

file name. A one-to-eight character alphanumeric field, containing A through Z, 0 through 9, and specialcharacters $ # @ + - (hyphen) : (colon) _ (underscore), that is part of the CMS file identifier and serves toidentify the file for the user.

file type. A one-to-eight character alphanumeric field, containing A through Z, 0 through 9, and specialcharacters $ # @ + - (hyphen) : (colon) _ (underscore), that is used as a descriptor or as a qualifier of the filename field in the CMS file identifier. See reserved file types.

G



gateway. The LU name of a VM system or TSAF collection that is a source for communications to an SNA-defined network or the target of communications from an SNA-defined network.

H

host. A VM control program in its capacity as manager of a virtual machine in which another operating systemis running. Contrast with guest.

host system. A data processing system that prepares programs and the operating environments for use byanother computer or controller.

I

initial program load (IPL). The initialization procedure that causes an operating system to begin operation. AVM user must IPL the specific operating system into the virtual machine that will control the user's work. Eachvirtual machine can be loaded with a different operating system.

input/output (I/O). (1) A device whose parts can do an input process and an output process at the same time.(2) A functional unit or channel involved in an input process, output process, or both, concurrently or not, and tothe data involved in such a process.

interactive. The classification given to a virtual machine depending on this virtual machine's processingcharacteristics. When a virtual machine uses less than its allocation time slice because of terminal I/O, the virtualmachine is classified as being interactive. Contrast with noninteractive.

invoke. To start a command, procedure, or program.

L

local. Two entities (for example, a user and a server) are said to be local to each other if they belong to the samesystem within a collection or to the same node within an SNA system. Contrast with remote.

local node. Is the name of the PVM node controlling your workstation.

logoff. The procedure by which a user ends a terminal session.



LOGMSG. Area of the PVM Initial Menu or the PVM Selection Menu where messages display from the PVMoperator.

logon. The procedure by which a user begins a terminal session.

M

macro. Synonym for macrodefinition and macroinstruction.

macrodefinition. A set of statements that defines the name of, format of, and conditions for generating asequence of assembler language statements from a single source statement. Synonymous with macro.

macroinstruction. In assembler language programming, an assembler language statement that causes theassembler to process a predefined set of statements called a macrodefinition. The statements usually producedfrom the macrodefinition replace the macroinstruction in the program. Synonymous with macro.

message. Data sent from a source application to a target application program in a conversation.

MPVM. VM/Pass-Through Facility Multiple Session Application support for establishing multiple sessionswhile you are still logged on to your host CMS system. MPVM is a component of VM/Pass-Through FacilityVersion 2.

N

NAMES file entry. In the MSAF NAMES or MSAFSYS NAMES file, a nickname tag/value pair and a set ofrelated tag/value pairs that further describe the nickname.

network. Any set of two or more computers, workstations, or printers linked in such a way as to let data betransmitted between them.

node. (1) A single processor or a group of processors in a teleprocessing network. (2) A computer, workstation,or printer, when it is participating in a network.

node identifier (node ID). The name by which a node is known to all other nodes in a network.

P



parameter. A variable that is given a constant value for a specified application and that may denote theapplication.

PASSTHRU. Single session support for CMS users.

password. In computer security, a string of characters known to the computer system and a user, who mustspecify it to gain full or limited access to a system and to gain full or limited access to a system and to the datastored within it.

path. In APPC/VM or IUCV, a connection between two application programs that are on the same or differentsystems. Paths have names assigned to them.

PF key. Programmed function key.

port. An access point for data entry or exit.

PROFILE EXEC. A special EXEC procedure with a file name of PROFILE that a user can create. Theprocedure is usually executed immediately after CMS is loaded into a virtual machine (also known as IPLCMS).

programmed function (PF) key. On a terminal, a key that can do various functions selected by the user ordetermined by an application program.

PVM. VM/Pass-Through Facility.

PVMG. VM/Pass-Through Facility (PVM) Gateway component (PVMG server).

R

real address. The address of a location in real storage or the address of a real I/O device.

remote. Two entities (for example, a user and a server) are said to be remote to each other if they belong todifferent systems within a collection, or to different nodes within an SNA network. Contrast with local.

remote operator console facility (ROCF). A 4300 Series support processor licensed internal code function thatpermits communication from a remote console for functions like IML or IPL using a switched line. TheVM/Pass-Through Facility program provides a communication vehicle that lets any of its supported displaystations serve as this remote console.

S

screen. An illuminated display surface; for example, the display surface of a CRT. Synonymous with physicalscreen.



scrolling. (1) Moving a display image vertically or horizontally to view data not otherwise visible within theboundaries of the display screen. (2) Performing a scroll up, scroll down, scroll right, or scroll left operation.

separator. Synonym for delimiter.

server. (1) The general name for a virtual machine that provides a service for a requesting virtual machine. (2)The program that responds to a request from another computer or the same computer through SRPI. Contrastwith requester.

session. The SNA term for a connection between two LUs. The LUs involved allocate conversations acrosssessions.

SMSG function. A CP function that lets a virtual machine send a special message to another virtual machineprogrammed to accept and process the message. See special message.

SNA. Systems Network Architecture.

special message. A data transmission, made up of instructions or commands, sent from one virtual machine toanother by means of the SMSG function. A special message is processed by the receiving virtual machine anddoes not appear on the receiver's console. See SMSG function.

syntax. The rules for the construction of a command or program.

System Product Editor. The CMS facility, containing the XEDIT command and XEDIT subcommands andmacros, that lets a user create, change, and manipulate CMS files.

Systems Network Architecture (SNA). The description of the logical structure, formats, protocols, andoperational sequences for transmitting information units through and controlling the configuration and operationof networks.

T

target. One of many ways to identify a line to be searched for by the System Product Editor. A target can bespecified as an absolute line number, a relative displacement from the current line, a line name, or a stringexpression.

U

user. Anyone who requests the services of a computing system.

user ID. User identification.



V

virtual machine (VM). In VM, a functional equivalent of a computing system. On the 370 Feature of VM, avirtual machine operates in System/370 mode. On the ESA Feature of VM, a virtual machine operates inSystem/370, 370-XA, or ESA/370 mode. Each virtual machine is controlled by an operating system. VMcontrols the concurrent execution of multiple virtual machines on an actual processor complex.

Virtual Telecommunications Access Method (VTAM). An IBM licensed program that controlscommunication and the flow of data in a computer network. It provides single-domain, multiple-domain, andmultiple-network capability. VTAM runs under MVS, OS/VS1, VM/ESA, and VSE.

VM/Pass-Through Facility. A facility that lets VM users interactively access remote system and processornodes. These can be remote IBM 4300 processors, other VM systems, with or without this facility installed, orSystem/370- compatible non-VM systems.

VTAM. Virtual Telecommunications Access Method.

W

workstation. An I/O device from which jobs can be submitted to a host system for processing, or to whichoutput can be returned, or both.

X

XEDIT. See System Product Editor.

Numerics

3270. Refers to a series of IBM display devices; for example, the IBM 3275, 3276 Controller Display Station,3277, 3278, and 3279 Display Stations, the 3290 Information Panel, and the 3287 and 3286 printers. A specific



device type is used only when a distinction is required between device types. 327x refers to a series of IBMcontrol unit devices; for example, the IBM 3271, 3274 control unit devices.

BIBLIOGRAPHY Bibliography

This bibliography lists the books that provide additional information about your system. The titles that are referenced in this publication are marked with a box (þ).

Subtopics:

BIBLIOGRAPHY.1 PVM and Related Publications

BIBLIOGRAPHY.1 PVM and Related Publications

The following table lists the VM/Pass-Through Facility publications that are helpful when using this book.

___ _______________________________________________________ ____________ | | Title | Order | | | | Number | |___|_______________________________________________________|____________| | VM/Pass-Through Facility | |___ _______________________________________________________ ____________| | þ | Programming Reference | SC24-5556 | |___|_______________________________________________________|____________| | þ | Administration and Operation | SC24-5557 | |___|_______________________________________________________|____________|

___ Bill-of-Forms ______________________________________________________ | | | The order number for ordering the VM/Pass-Through Facility Version 2 | | library is SBOF-3273. This provides you with a single copy of the | | following: | | | | GX24-5622-00 Introducing VM/Pass-Through Facility Version 2 | | SC24-5555-00 VM/Pass-Through Facility User's Guide | | SC24-5556-00 VM/Pass-Through Facility Programming Reference | | SC24-5557-00 VM/Pass-Through Facility Administration and | | Operation | | | | You can separately order the following: | | | | SX24-5255-00 Binder Insert | | (Unit of measure is one per book and is | | applicable for the VM/Pass-Through Facility | | Administration and Operation book and the |



| VM/Pass-Through Facility Programming | | Reference.) | | SX24-0258-00 White Binder | | (Unit of measure is one per book and is | | applicable for the VM/Pass-Through Facility | | Administration and Operation book and the | | VM/Pass-Through Facility Programming | | Reference.) | | | |________________________________________________________________________|

Subtopics:

BIBLIOGRAPHY.1.1 VM/ESA (ESA Feature) Publications BIBLIOGRAPHY.1.2 VM/ESA (370 Feature) Publications BIBLIOGRAPHY.1.3 VM/ESA Common Publications

BIBLIOGRAPHY.1.1 VM/ESA (ESA Feature) Publications

The following ESA Feature publication may be helpful.

___ _______________________________________________________ ____________ | | Title | Order | | | | Number | |___|_______________________________________________________|____________| | þ | VM/ESA CP Command and Utility Reference | SC24-5519 | |___|_______________________________________________________|____________|

BIBLIOGRAPHY.1.2 VM/ESA (370 Feature) Publications

The following table lists each 370 Feature publication by task-oriented category.

___ _______________________________________________________ ____________ | | Title | Order | | | | Number | |___|_______________________________________________________|____________| | þ | VM/ESA CP General User Command Reference for 370 | SC24-5433 | |___|_______________________________________________________|____________|

BIBLIOGRAPHY.1.3 VM/ESA Common Publications

The following VM/ESA Common publication may be helpful.

___ _______________________________________________________ ____________



| | Title | Order | | | | Number | |___|_______________________________________________________|____________| | þ | VM/ESA CMS Command Reference | SC24-5461 | |___|_______________________________________________________|____________| | | VM/ESA CMS Primer | SC24-5458 | |___|_______________________________________________________|____________| | | VM/ESA CMS User's Guide | SC24-5460 | |___|_______________________________________________________|____________| | | VM/ESA XEDIT Command and Macro Reference | SC24-5464 | |___|_______________________________________________________|____________| | | VM/ESA XEDIT User's Guide | SC24-5463 | |___|_______________________________________________________|____________| | Reference Summaries | |___ _______________________________________________________ ____________| | | VM/ESA CMS Command Reference Summary | SX24-5249 | |___|_______________________________________________________|____________| | | VM/ESA CMS Primer Summary of Commands | SX24-5247 | |___|_______________________________________________________|____________| | | VM/ESA Procedures Language VM/REXX Reference Summary | SX24-5251 | |___|_______________________________________________________|____________| | | VM/ESA XEDIT Command Reference Summary | SX24-5250 | |___|_______________________________________________________|____________|

INDEX Index

A

Accessing PVM MPVM, 2.6.1 multiple sessions, 2.6.2.2 PVM from within CMS, 2.4 SNA network, 2.3 using CP DIAL command, 2.2 using PASSTHRU command, 2.4 using VTAM LOGON command, 2.3 address field, Initial Menu, 2.1.1 ALARM, setting to OFF using MPVM SET, 2.6.7 applications, accessing, 2.6.2.2 assigning PF key definitions in MPVM, 2.6.7 asterisks, specifying with PASSTHRU command, 2.4.1

B

BEEPZ, setting to OFF with MPVM SET, 2.6.7 bibliography, BIBLIOGRAPHY



Bypassing menus MPVM Selection Menu, 2.6.2.2 PVM Selection Menu, 2.4 bypassing the NOTEPAD facility, PASSTHRU, 2.4.1

C

changing or switching among MPVM sessions, 2.6.3 choosing sessions, 2.6.1 CINIT data, 2.3 cluster number, Initial Menu, 2.1.1 CMD command, 3.0 CMS Commands NAMES, 2.4.1.1.3 prefixing CMS commands with an escape character in MPVM, 2.6.8 SYNONYM, 2.4.1.1.3 CMS names file, 2.4.1.1.3 command line, of VM logon screen, 2.2 Commands ?MPVM, 2.6.8 CMD, 3.0 CPQ, 3.0 DIAL (CP command), 2.2 entering from CMS, 3.0 entering general user PVM server, 3.0 general user MPVM, 2.6.8 general user PVM, 3.0 MPVM, 2.6.8 MSG, 3.0 NOTEPAD, MPVM environment, 2.6.8 PMSG, 3.0 QUERY, 2.6.8 3.0 in MPVM environment, 2.6.8 SELECT, 2.6.8 SET, 2.4.1.1.1 2.6.8 in MPVM, 2.6.8 using CP SET in PASSTHRU, 2.4.1.1.1 SHOW, 3.0 SMSG (CP command), 3.1 TEMPDISC, using in MPVM environment, 2.6.8 Copying Screen Images in MPVM environment, 2.6.4 partial screen images, 2.6.4 in PASSTHRU environment, 2.4.2 CP Commands DIAL, 2.2 prefixing CP commands with an escape character in MPVM, 2.6.8 SET, 2.4.1.1.1 SMSG, 3.0 CPQ command, 3.0 current session, in MPVM, 2.6.2.2

D



Defaults character string for session terminate function, 2.4.1 escape character prefix, MPVM, 2.6.2.2 for YES parameter, PASSTHRU command, 2.4.1 PVM user ID for PASSTHRU command, 2.4 session terminate string for PASSTHRU command, 2.4.1 defaults, specifying in MPVM NAMES file, 2.6.9.1 defining PF key to issue PASSTHRU command, 2.4.1.1.1 destination, PVM Selection Menu, 2.5.1 device error, A.2 device information, displaying, 3.0 dialing a second-level operating system, A.2 dialing PVM, 2.2 displaying MPVM variable settings, 2.6.7

E

ending an MPVM session, using LOGOFF command, 2.6.9.2 ending sessions, PVM Selection Menu, 2.5.1 entries for NAMES file, MPVM, 2.6.5 error and informational messages, getting HELP, 1.3 escape, setting an escape character in MPVM, 2.6.8 escaped character prefix, using, 2.6.8 Escaped Command Facility, in MPVM description of facility, 1.1 sending commands to your host system, 2.6.8 specifying escape character prefix, 2.6.2.2 establishing multiple sessions, 2.6.1

F

Facilities, PVM CP Logical Device Support Facility,, A.3 MPVM Escaped Command Facility, 1.1 PASSTHRU NOTEPAD, 2.4.1 Functions NOTEPAD, in PASSTHRU, 2.4.2 session terminate, PASSTHRU, 2.4.1 temporary disconnect (TDISC), PASSTHRU, 2.4.1

G

gateway, 1.2 General User Commands MPVM commands, 2.6.8 PVM Server Commands, 3.0 getting information about MPVM sessions, 2.6.3.2



getting online help, 1.3 global variable, MPVM, 2.6.5.1 GRAF address on CP DIAL command, A.2

H

HELP, online for MPVM, 1.3 HELP, online for PASSTHRU, 1.3 helpful tips for using PASSTHRU command, 2.4.1.1 host session, in MPVM, 2.6.1

I

I/O verification, A.3 Initial Menu, 2.1 Input/Output (I/O) Verification IOV option on VTAM LOGON command, 2.3 Verify field on PVM Selection Menu, 2.5.1 where indicators are displayed, A.3 YES parameter, PASSTHRU command, 2.4.1 input/output verification, 2.4.1 invoking MPVM, 2.6.1 invoking PASSTHRU automatically, 2.4.1.1.2

K

Key Settings defining in MPVM, 2.6.6 for the PASSTHRU command, 2.4.1.1.1

L

Language command prefix for PVM commands, 3.3 field, on PVM Selection Menu, 2.5.1 parameter for PASSTHRU command, 2.4.1 language IDs, 2.4.1 local node, Initial Menu, 2.1.1 local variable, MPVM, 2.6.5.1 logging off sessions/applications, PASSTHRU, 2.4.1 LOGMSG area, PVM Selection Menu, 2.5.1 LOGOFF Command ending an application or session, 2.4.1



in PASSTHRU, 2.4.1 LU name, PVM Selection Menu, 2.5.1

M

macro, WHERE for MPVM sessions, 2.6.3.2 maximum allowable number of MPVM sessions per user, 2.6.2.2 maximum time limits, MPVM, 2.6.8 maximum time limits for MPVM sessions, 2.6.8.1 menu, MPVM, selecting sessions, 2.6.1 messages, getting online HELP, 1.3 MPVM command, 2.6.1 MPVM component, 1.0 MPVM NAMES file, 2.6.4.1 MPVMDATA, default file type for MPVM's NOTEPAD file, 2.6.4 MPVMSYS NAMES file, 2.6.5 MSG command, 3.0 multiple applications, accessing, 2.6.2.2 multiple sessions, accessing, 2.6.2.2 multiple sessions, MPVM selection menu, 2.6.1 MVS, example, A.2

N

names file entries, MPVM, 2.6.5 names file, MPVM, 2.6.5 network status, displaying, 3.0 nicknames on MPVM selection menu, 2.6.1.1 node types, PVM Selection Menu, 2.5.1 NOTEPAD Facility sample PASSTHRU DATA file, 2.4.2 using in MPVM environment, 2.6.4 using, after issuing PASSTHRU, 2.4.2 NOTEPAD, using in MPVM environment, 2.6.8

O

online HELP, 1.3 ordering publications, BIBLIOGRAPHY.1 origin, displaying, 3.0

P

Parameters



for MPVM command, 2.6.2.1 for PASSTHRU command, 2.4.1 partial screen images, saving in MPVM, 2.6.4 Pass-Through Facility Selection Menu, sample, 2.4 PASSTHRU command selecting a target system, sample, 2.4.2 PASSTHRU DATA file, default for NOTEPAD, 2.4.2 path, displaying, 3.0 personal MVPM NAMES, 2.6.4.1 PMSG command, 3.0 port address, PVM Selection Menu, 2.5.1 port number, Initial Menu, 2.1.1 precedence, PF keys in MPVM, 2.6.4.1 preventing 3270 I/O errors, A.0 profile exec, adding a PASSTHRU command, 2.4.1.1.1 Program Error Recovery screen, A.0 PVM components, 1.0 PVM publications, BIBLIOGRAPHY PVM Selection Menu Initial Menu, 2.1 MPVM Selection Menu, 2.6.1 PVM Selection Menu, 2.5 PVMG component, 1.0

Q

question mark, default escape character in MPVM, 2.6.8

R

R3270, Initial Menu, 2.1.1 real address, Initial Menu, 2.1.1 real address, PVM Selection Menu, 2.5.1 recovering from a 3270 I/O error, A.0 related publications, BIBLIOGRAPHY.1 remote 3270 address, PVM Selection Menu, 2.5.1 REXX exec, creating, 2.4.1.1.2 ROCF, PVM Selection Menu, 2.5.1 route, 2.4.1

S

sample, displaying multiple sessions, 2.6.9 sample, entries in a personal MPVM NAMES file, 2.6.9 saving screen images, 2.4.2 screen images, saving in MPVM, 2.6.4 secondary system node ID, 2.4.1 SELECT command, overview, 2.6.3 SELECT, MPVM command, 2.6.8



selecting MPVM sessions, 2.6.1 selection menu, 2.6.1 sending a message, 3.0 sequence, displaying multiple sessions, 2.6.9.2 server, entering general user PVM server commands, 3.0 Servers PVM, 1.0 PVMG, 1.0 session terminate function, specifying with PASSTHRU command, 2.4.1 session terminate string, 2.5.1 session, host in MPVM, 2.6.1 SET command, using in MPVM environment, 2.6.8 SET ESCAPE, MPVM command, 2.6.8 setting a PF key as NOTEPAD, in MPVM, 2.6.9.1 setting a PF key in MPVM, 2.6.4.1 setting values for MPVM variables, 2.6.7 SHOW command, 3.0 SNA LU name, PVM Selection Menu, 2.5.1 SNA network, accessing, 1.1 starting an MPVM session, 2.6.1 subtags, MPVM, 2.6.5 switching among MPVM sessions, 2.6.6 switching between PVM sessions, 2.4.1.1.1 synonym, creating for PASSTHRU command, 2.4.1.1.4 system NAMES file, MPVMSYS, 2.6.5.1 system-wide file, MPVM, 2.6.5 Systems Network Architecture, accessing, 1.1

T

tags, in MPVM NAMES file, 2.6.5 target application, MPVM, 2.6.3 target MPVM names file entry, 2.6.9.1 TEMPDISC, in MPVM environment, 2.6.8 temporary disconnect function, specifying with PASSTHRU command, 2.4.1 time limits, MPVM, 2.6.8 tips for using PASSTHRU command, 2.4.1.1

U

User ID for host system, 2.6.1 for MPVM system, 2.6 for systems your are accessing, 2.6.1

V

Values finding out values of MPVM variables, 2.6.7



Variables changing values of MPVM variables, 2.6.7 virtual address, specifying on CP DIAL command, A.2 virtual machine, user ID for PVM, 2.2 VM/Pass-Through Facility Selection Menu, sample, 2.4 VTAM LOGON command DATA options, 2.3

W

ways to access PVM, 2.0 WHERE macro, for MPVM sessions, 2.6.3.2

X

XEDIT, using with NOTEPAD, 2.4.2

COMMENTS Readers' Comments VM/Pass-Through Facility User's Guide Version 2

Publication No. SC24-5555-00

IS THERE ANYTHING YOU ESPECIALLY LIKE OR DISLIKE ABOUT THIS BOOK? Feel free to comment on specific errors or omissions, accuracy, organization, or completeness of this book.

IBM may use and distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you, and all such information will be considered nonconfidential.

Print this topic and mail it to:

International Business Machines Corporation Information Development Department G60 PO Box 6 Endicott, New York 13760



___ Note. ______________________________________________________________ | | | Do not use this form to report system problems or to request copies of | | publications. Instead, contact your IBM representative or the IBM | | branch office serving you. | | | |________________________________________________________________________|

Would you like a reply? ___YES ___NO

Name . . . . . . . . . _______________________________________________ Company or Organization _______________________________________________ Address . . . . . . . . _______________________________________________ _______________________________________________ _______________________________________________ Phone No. . . . . . . . _______________________________________________

IBM Library Server Print Preview

DOCNUM = SC24-5555-00 DATETIME = 11/05/91 14:56:42

BLDVERS = 1.2 TITLE = User's Guide

AUTHOR = COPYR = © Copyright IBM Corp. 1991

PATH = /home/webapps/epubs/htdocs/book

This Library Server will be sunset on June 1, 2019 Please see the IBM Z Library Archive

VM/Pass-Through Facility - IBM · of IBM systems, consult the latest IBM System/370, 30xx, 4300,...

Documents

Transcript of VM/Pass-Through Facility - IBM · of IBM systems, consult the latest IBM System/370, 30xx, 4300,...