automating access to the networkglobalnetwork.support.att.com/att/advdisp.pdfchapter 1,...

Automating Access to the Network

GC34-2200-02

NOTE: Before using this information and the product it supports, be sure to read the general information under “Notices” on page vii.

Third Edition (May 1995)

This book is a major revision and replaces GC34-2200-01. New editions will reflect changes in proce-dures or technical details.

Books are not stocked at the address given below. Requests for copies should be made to your marketing representative.

A form for readers’ comments is provided at the back of the book. If you do not have access to this form, address comments to: Advantis, Department RD10, P.O. Box 20143, Tampa, FL 33633-0872, U.S.A.

Advantis may use or distribute whatever information you supply in any way it believes appropriate without incurring any obligation to you.

© Copyright IBM Corp. 1990. Copyright Advantis 1995. All rights reserved.Note to U.S. Government Users - Documentation related to restricted rights - Use, duplication, or disclosure is subject to restrictions and provisions of FAR 52.227-14 or DFAR 252.227-7013, as appli-cable.

© Copyright Advantis 1995 iii

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTrademarks and service marks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

To the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixAbout this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixRelated books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xHow to use this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. Connecting to the network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1Connecting to the network with an attached network terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2Connecting to the network with a network-attached terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Connecting through the Network Control Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3A. 3270 to NCP—leased . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3B. 3270 to NCP—dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Connecting through the Series/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4Connecting through Series/1 or the IN Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

C. SS/ELM to Series/1 or the IN Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5D. SNA/A to Series/1 for INPCS—Entry or the IN Gateway . . . . . . . . . . . . . . . . . . . . . . . . .1-5E. SNA/S 3270 full-screen to Series/1 or the IN Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6F. SNA/S RJE to Series/1 or the IN Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6G. SNA/S SNUF to Series/1 or the IN Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6

Connecting through Series/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7H. BSC 3275 to Series/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7I. BSC RJE to Series/1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7

Connecting through the 3708 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8J. SS/EFS to 3708 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8

Connecting through the IN Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8K. SS/EFS to the IN Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8L. HPO to the IN Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9

iv Automating Access to the Network

Chapter 2. Introducing the programmable interface . . . . . . . . . . . . . . . . . . . . 2-1Accessing the programmable interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Using a full-screen device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Using a line-mode device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Using an SNA/S RJE device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Chapter 3. Writing your programmable interface . . . . . . . . . . . . . . . . . . . . . . . 3-1Suggestions for programming to the interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Syntax for logging on for users with full-screen and line-mode devices . . . . . . . . . . . . . . . . . . . . . . . 3-2

LOGON examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Syntax for selecting a single product for users with full-screen and line-mode devices . . . . . . . . . . . 3-5

SELECT examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Syntax for displaying a product selection menu for users with full-screen devices . . . . . . . . . . . . . . 3-6Logging on and selecting a product or product menu for users with full-screen devices . . . . . . . . . 3-7Syntax for browsing messages for users with full-screen devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

MESSAGE examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Logging on and enabling users with full-screen devices to browse user messages . . . . . . . . . . . . . . 3-11

Getting help with a full-screen device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Logging on and selecting a product for users with line-mode devices . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Getting HELP with a line-mode device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Syntax for logging off for users with full-screen and line-mode devices . . . . . . . . . . . . . . . . . . . . . . 3-17

LOGOFF examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Chapter 4. Sample flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Examples for full-screen devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Logging on, selecting a product, and logging off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Logging on and changing a password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Logging on with MESSAGESTATUS=YES and displaying a product selection menu . . . . . . . . 4-6Recovering from an unsuccessful logon attempt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Browsing messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Examples for line-mode devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Logging on, selecting a product, and logging off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Logging on and changing a password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15Recovering from an unsuccessful logon attempt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

Appendix A. Using direct logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1Syntax for direct logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1

Examples of direct logon format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3Logging off after you use direct logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3

Examples of format for logging off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-4

Contents v

Appendix B. Using batch logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Creating a batch logon card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1Using the batch logon interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Appendix C. TWX line-mode messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Appendix D. Example of INPCS—Entry logon . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Appendix E. Example of Advantis Passport logon . . . . . . . . . . . . . . . . . . . . . .E-1

Appendix F. Messages and codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-1USSMSG10 welcome messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-23708 welcome message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-3IN Gateway enhanced full—screen (EFS) welcome message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-3General messages (SVMI0xxC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-3Logon request messages (SVMI1xxC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-5Application selection and logoff messages (SVMI2xxC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-18Message Service request messages (SVMI3xxx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-22Product Menu request messages (SVMI4xxx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-24Messages generated by other functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .F-25

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-5

vi Automating Access to the Network

© Copyright Advantis 1995 vii

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Notices

Advantis* provides IBM Global Network services in the United States. References in this publication to Advantis products, programs, or services do not imply that Advantis intends to make these available in all countries in which Advantis operates. Any reference to an Advantis product, program, or service is not intended to state or imply that only Advantis’ product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe on any of Advantis’ intellectual property rights or other legally protected rights may be used instead of the Advantis product, program, or service, subject to the terms contained in the appli-cable license agreements. Evaluation and verification of operation in conjunction with other products, programs, or services, except those expressly designated by Advantis, are the user’s responsibility.

Advantis 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. Please send license inquiries, in writing, to the Advantis Legal Department, Advantis, Schaumburg, IL, 60173.

This publication may contain examples of data and panels used in daily business operations. To make such examples as complete as possible, the names of individuals, companies, brands, and products might be used. All such names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

Trademarks and service marksThe following terms, denoted by an asterisk (*) in this publication, are trademarks of Advantis:

Advantis

All other trademarks, denoted by a double asterisk (**) in this publication, are the property of their respective owners.

viii Automating Access to the Network

© Copyright Advantis 1995 ix

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . To the reader

Please note that Advantis provides IBM Global Network services only in the United States. In other countries, IBM Global Network services may be provided by the IBM Information Network or another company. Similarly, references in this document to your network specialist refer to the representative at the company that provides your network services. For instance, in the U.S., this person may be an Advantis Specialist, while in Germany, the person may be an IBM Marketing Representative.

The network provides several ways for its customers to log on to and use the services:

n Regular interactive logon

n Programmable interface

n Direct logon (described in Appendix A‚ “Using direct logon”)

n Batch logon (described in Appendix B‚ “Using batch logon”)

This book describes the programmable interface, direct logon, and batch logon. It also describes the various connectivity methods that enable users to first gain access to the network.

This book is for programmers who are responsible for writing a programmable interface to the network.

About this bookThis book is organized as follows:

n Chapter 1, “Connecting to the network,” describes the methods of connecting to the network.

n Chapter 2, “Introducing the programmable interface,” gives an overview of the programmable interface and how to access it.

x Automating Access to the Network

n Chapter 3, “Writing your programmable interface,” describes the programmable logon requirements and formats for both full-screen (LU 2) and line-mode (LU 1) sessions. This chapter also explains how you can select individual applications, select a product menu, browse messages, and log off the network.

n Chapter 4, “Sample flows,” illustrates sample flows for LU 2 and LU 1 sessions.

n Appendix A, “Using direct logon,” describes a form of automated logon for users on a network attached to the network.

n Appendix B, “Using batch logon,” describes how to create a batch logon card and how to use the batch logon interface.

n Appendix C, “TWX line-mode messages,” illustrates teletypewriter exchange service (TWX) line-mode messages.

n Appendix D, “Example of INPCS—Entry logon,” shows an example of an INPCS—Entry logon script. Each entry is explained in detail.

n Appendix E, “Example of Advantis Passport logon,” shows an example of an Advantis Passport logon script. Each entry is explained in detail.

n Appendix F, “Messages and codes,” gives a detailed explanation of all applicable messages and codes.

This book also contains a glossary and an index.

Related booksn Advantis Passport/DOS User’s Guide, GC34-2245

n Advantis Passport/DOS Programming Guide, GC34-2244

n Advantis Passport for Macintosh Computers User’s Guide, GC34-2270

n Advantis Passport/2 User’s Guide, GC34-2241

n Advantis Passport for Windows User’s Guide, GC34-2256

n INPCS 3270 for Windows, GC34-2311

n INPCS 3270 for OS/2 User’s Guide, GC34-2310

n INPCS 3270 for DOS Programming Guide, GC34-2309

n INPCS 3270 for DOS User’s Guide, GC34-2308

n IBM Information Network Series/1 SNA Gateway Interface Specifications, GC34-2224

n Using Remote Job Entry on the IBM Information Network, GC34-2219

To the reader xi

How to use this bookChapter 1, “Connecting to the network,” contains information that most readers will find helpful. Read this chapter before using other parts of this guide.

The step-by-step instructions in this book tell you what to send to the network in your programming code. For example, the instruction “send /pi and an Enter keystroke” means that you should write /pi followed by the code you use to indicate an Enter keystroke and send this programming information to the network.

Command examples are provided throughout this book and, for the most part, are printed in lowercase letters. You can type commands in uppercase or lowercase letters when programming; the programmable interface is not case sensitive. However, the letter L is printed in some examples as a capital letter to prevent you from confusing it with a capital i or a number 1. When typing commands, you can use a lowercase L. Throughout this book, the following symbols and type conventions define the instruction format of a command:

The symbols and type conventions described above are not part of the command syntax. You do not need to use them when sending commands.

Symbol / Type convention Description

Braces { } Delimit parameters from which choices are made.

Vertical bar | Indicates that a choice is to be made.

Square brackets [ ] Denote options. Anything enclosed in square brackets may or may not be coded, depending on which option you want to use.

Boldface text Indicates material to be typed such as a command or keyword.

Small capitals Denote commands, for example, SELECT.

xii Automating Access to the Network

© Copyright Advantis 1995 1-1

Chapter 1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting to the network

This chapter explains how to connect to the network. The initial responses you see depend on your hardware and your access to the network. The following two main categories of attachment to the network can use the programmable interface:

1 Attached network terminals (ANTs) are attached indirectly to the network through another network.

These can be leased-line or dial-line attached to your network:

a Full-screen (LU 2)

b Line-mode (LU 1)

2 Network-attached terminals (NATs) are attached directly to the network. These are further classified into leased and dial types:

a Leased-line or dial-line attached through a Network Control Program (NCP)—3270 to NCP (LU 2)

b Dial-line attached through a Series/1

1) Start-Stop/Enhanced Line Mode (SS/ELM) used with LU 1 devices

2) Systems Network Architecture/Asynchronous (SNA/A) for IBM Infor-mation Network Personal Connectivity Service (INPCS)—Entry used with LU 2 devices

3) Systems Network Architecture/Synchronous (SNA/S) used with LU 2 devices

4) Systems Network Architecture/Synchronous Remote Job Entry (SNA/S RJE) used with LU 1 devices

5) Binary Synchronous (BSC) 3275 used with LU 2 devices

6) Binary Synchronous Remote Job Entry (BSC RJE) used with LU 1 devices

1-2 Automating Access to the Network

c Dial-line attached through a 3708—Start-Stop/Enhanced Full-Screen (SS/EFS) used with LU 2 devices

d Dial-line attached through the IN Gateway using Advantis Passport.

Connecting to the network with an attached network terminal

Attached network terminals (ANTs) are attached to another network either through a leased line or a dial connection. Using the programmable interface with an ANT, you can access the network as a full-screen (LU 2) device or as a line-mode (LU 1) device. You also can use the direct logon as described in Appendix A‚ “Using direct logon.”

The responses that an ANT sees when making selections from its network depend entirely on the software running in that network. For example, an LU 2 device might see the Welcome to Advantis panel, or it might see your own company’s logo, welcome panel, or the Network Message panel, USSMSG10.

Connecting to the network with a network-attached terminal

Network-attached terminals (NATs) attach directly to the network either through a leased line or a dial line. All programmable interface panels have unique alphanumeric IDs in the first 8 characters. Because the layout and design of panels may differ, look for this ID when you program to the programmable interface.

If you use Series/1 for BSC RJE, see Appendix B‚ “Using batch logon.”

The following sections describe the connections illustrated in the following diagram, as well as the respective system responses.

Connecting to the network 1-3

Connecting through the Network Control ProgramBoth connection types A and B in the diagram above attach to the network by way of the Network Control Program (NCP). Connection type A attaches through a leased line; connection type B attaches through a dial line.

A. 3270 to NCP—leasedThe 3270 to NCP leased-line connection is an LU 2 interface. Follow these steps to connect to the network:

1 Look for the Network Message panel, USSMSG10. See Appendix F‚ “Messages

NetworkAttachedTerminals(NATs)

3270 leased (LU 2)

3270 dial (LU 2)

SS/ELM (LU 1)

SNA/A (LU 2)

SNA/S RJE (LU 1)

SNA/S SNUF (LU 0)

BSC 3275 (LU 2)

SS/EFS to 3708 (LU 2)

HPO (LU 2)

BSC RJE (LU 1)

SNA/S 3270 full-screen(LU 2)

Series/1

3708/IN Gateway

IN Gateway

A

B

C

D

E

F

G

H

I

J

K

Examples

3270

3270

TWX

INPCS-EntryPC/3270

3274

3776

AS/400 SNUF

3275

277027803780

3101

3270 orPassport

or

Series/1

IN Gateway


and codes.”

2 Respond by sending any character to the system.

The system displays panel SVM0201P (the full-screen Welcome to Advantis panel).

3 To use the programmable interface, send: /pi and an Enter keystroke.

You can send this command from any input field, as described in Chapter 2, “Introducing the programmable interface.”

B. 3270 to NCP—dialThe 3270 to NCP dial-line connection is an LU 2 interface. Follow these steps to connect to the network:

1 Dial in.



You can send this command from any input field, as described in Chapter 2‚ “Introducing the programmable interface.”

Connecting through the Series/1The Series/1 provides dial-line access for the following terminal types:

n Asynchronous line mode (SS/ELM)n INPCS (SNA/A)n SNA dial (3270, RJE)n BSC 3275n BSC RJE

The Series/1 connections, C through I in the diagram, are described in the following sections.


Connecting through Series/1 or the IN Gateway

C. SS/ELM to Series/1 or the IN GatewayThe Series/1 provides support similar to the NTO support provided through the NCP. The Series/1 or IN Gateway support has several enhancements that are fully described in IBM Information Network Series/1 SNA Gateway Interface Specifications.

To connect to the network through SS/ELM to Series/1 or the IN Gateway, follow these steps:

1 Dial in.

2 Send a carriage return (CR) to set the auto speed (this is optional if you use 1200 bps).

The system displays SVM0201L (the Welcome to Advantis panel).

If, after a given period, the Series/1 does not receive a CR, or if it cannot determine the line speed, the port defaults to 1200 bps.

3 Issue the terminal SETMODE command (optional).

The terminal specifies some operating characteristics for the link between itself and the Series/1. To specify these characteristics, issue a terminal SETMODE command in response to the Welcome to Advantis panel.


You can send this command from any input field, as described in Chapter 2‚ “Introducing the programmable interface.”

D. SNA/A to Series/1 for INPCS—Entry or the IN GatewayThe Series/1 supports INPCS—Entry or PC/3270 access over an asynchronous link, using a link protocol similar to that used for SDLC. This is available in the U.S. only.

To connect to the network through SNA/A, for INPCS—Entry or PC/3270, follow these steps:

1 Dial in.



This can be in any input field, as described in Chapter 2‚ “Introducing the


programmable interface.”

For more information, see Appendix D‚ “Example of INPCS—Entry logon.”

E. SNA/S 3270 full-screen to Series/1 or the IN GatewayThis protocol provides SDLC dial support for a fixed configuration. You do not need to register your configuration requirements in advance.

To connect to the network through the SNA/S 3270 full-screen, follow these steps:

1 Dial in.



You can send from any input field, as described in Chapter 2‚ “Introducing the programmable interface.”

F. SNA/S RJE to Series/1 or the IN GatewayThis protocol provides SNA RJE workstation dial connectivity through the network.

To connect to the network through SNA RJE, follow these steps:

1 Dial in.

The Series/1 activates SNA support at the RJE workstation.

2 Send the VTAM LOGON command with the user data field containing the programmable interface request, as described in “Using an SNA/S RJE device” on page 2-4.

Errors detected by the network are shown as VTAM USS messages.

The system begins the session with the application.

G. SNA/S SNUF to Series/1 or the IN GatewayIf you use Systems Network Architecture Upline Facility (SNA/S SNUF), you log on to the network by way of the Application System/400* (AS/400*) Intersystem Commu-nications Function (ICF) ACQUIRE command.

Follow these steps:

a

NOTE: With INPCS—Entry or PC/3270, you can use the PCSLOGON to automate logon commands. See IBM Information Network Personal Connec-tivity Service Installation and Customization.


1 Issue the AS/400 ICF ACQUIRE command.

This command causes your system to dial in and identify your workstation. To identify your workstation, the system specifies an SNA exchange ID (XID) of 05600000. The SNUF LU must use local address 08.

You receive a bind, or an associated address, from the network.

An ICF return code of 0 indicates a successful bind by the network.

2 Send a network batch logon command in a format similar to this:

/*logon account,userid,password/newpass/vpass/*select product/*userdata

For more information, see Appendix B‚ “Using batch logon.”

The network responds by sending an end bracket indicator (EBI) to your workstation, followed by an UNBIND HOLD. You receive a bind from the product you selected. Your workstation is now in session with that product.

Connecting through Series/1

H. BSC 3275 to Series/1The Series/1 provides support for a 3270 data stream through BSC 3275. For more information, see IBM Information Network Series/1 SNA Gateway Interface Specifica-tions.

To connect to the network through BSC 3275, follow these steps:

1 Dial in.

The system displays the Series/1 welcome message “Network connecting complete, port address is xx. Please record terminal ID yy.”

The system then displays panel SVM0201P (the Welcome to Advantis panel).



I. BSC RJE to Series/1This protocol allows 2770, 2780, and 3780 BSC RJE workstations to be supported through the Series/1 and to be supported on the network as 3776 workstations.

NOTE: This protocol does not support the programmable interface. For instructions on how to connect to the network through BSC RJE, see Using Remote Job Entry on the IBM Information Network. For the syntax of batch logon, see Appendix B‚ “Using batch logon.”


Connecting through the 3708There is one dial-line method of connection to a 3708 full-screen protocol converter in the network. Connecting from SS/EFS to the 3708 provides protocol conversion from SS/ASCII to full-screen 3270.

J. SS/EFS to 3708To connect to a 3708 in the network using SS/EFS, follow these steps. If you do not want to use the type ahead feature, turn off this feature as the last part of the logon procedure.

1 Dial in.

The 3708 displays the message “Enter terminal type.”

2 Send: terminal type and an Enter keystroke, replacing terminal type with the actual terminal type.

The system displays panel SVM0201P (the Welcome to Advantis panel).



Connecting through the IN GatewayThere is one dial-line method of connection to an IN Gateway full-screen protocol converter in the network. Connecting from SS/EFS to the IN Gateway provides protocol conversion from SS/ASCII to full-screen 3270.

K. SS/EFS to the IN GatewayTo connect to the IN Gateway in the network using SS/EFS, follow these steps:

1 Dial in.

2 Enter a space after you receive the connect message.

The IN Gateway displays the message “Type the number of your terminal.”

3 Send: number of terminal and an Enter keystroke.

The system displays panel SVM0201P (the Welcome to Advantis panel).

4 For a list of valid terminal types, press Enter.




L. HPO to the IN GatewayThe IN Gateway supports HPO protocol access over an asynchronous link using a link protocol similar to that used by high-level data link control (HDLC). The Passport/INPCS 3270 products support the HPO protocol.

To connect to the network using HPO for Passport/INPCS 3270, follow these steps:

1 Dial in using Passport /INPCS 3270.




Abbreviations and acronymsThis book contains many abbreviations and acronyms. In some cases, you may be more familiar with the abbreviated form. The definitions are listed below, but only the abbreviations or acronyms are used throughout the rest of this book.

NOTE: With Passport/INPCS 3270, you can use HPOAUTO to automate logon. For more information, see Appendix E‚ “Example of Advantis Passport logon.”

Abbreviation or acronym

Description

ANT Attached network terminal

AS/400 Application System/400

ASCII American National Standard Code for Information Inter-change

BPS Bits per second

BSC Binary synchronous (or bisynchronous)

EBCDIC Extended binary-coded decimal interchange code


HPG High-performance gateway

HPO High-performance option

ICF Intersystem Communications Function

INGW Intelligent Network Gateway

LU Logical unit

NAT Network-attached terminal

NCP Network Control Program

NTO Network terminal option

PC/3270 IBM Personal Computer/3270

RJE Remote job entry

SNA Systems Network Architecture

SNA/A Systems Network Architecture/asynchronous

SNA/S Systems Network Architecture/synchronous

SNUF SNA Upline Facility

SS/EFS Start-stop/enhanced full screen

SS/ELM Start-stop/enhanced line mode

TSO Time-sharing option

TWX Teletypewriter exchange service

USS Unformatted system services

USSMSG A VTAM Unformatted System Services message

VTAM Virtual Telecommunications Access Method

3270 3270 Personal Computer

3275 3275 Display Station

3708 3708 Protocol Converter

Abbreviation or acronym

Description


Chapter 2

Introducing the programmable

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . interface

The programmable interface provides a consistent interface to automate access to applications your users want to use on the network. This means that users no longer need to go through an interactive procedure to log on and select the application they want to work with. Users also can use an automatic logoff.

The programmable interface supports two SNA LU types: line-mode (LU 1) and full- screen (LU 2). The network recognizes LU type 0 as either LU 1 or LU 2; LU 0 is supported as whichever LU type it emulates.

With the programmable interface you can:

n Log on to the networkn Change your network passwordn Change your password for your eligible application productsn Select an application that runs on the networkn Specify the language you want to usen Find out if any new messages have arrivedn Find out if previously displayed messages are still availablen Log off the network

You also can enable users with full-screen devices to:

n Exit from the programmable interface to browse messages interactivelyn Resume the programmable interface after browsing messagesn Transfer control to a product selection menu after browsing messagesn Exit from the programmable interface to a product selection menu

If you have been programmed to the network interactive interface (either full-screen or line-mode), you need to change your existing programs to use the new program-mable interface. The existing interactive interface is not supported for automated access and is subject to change at any time. For more specific details, contact your marketing representative.

If you use an ANT, direct logon is available to you to avoid interactive panels on your own network. With the direct logon, include the logon data in the command you use to access the network. See Appendix A‚ “Using direct logon.”


Accessing the programmable interfaceThe programmable interface program examines the data it receives from the Welcome to Advantis panel and determines if you are attempting to access the network using the programmable interface.

Various connectivity possibilities are described in Chapter 1‚ “Connecting to the network.” The following sections summarize how you initially connect to the programmable interface.

Using a full-screen device If you connect to the network through a full-screen device, your device receives panel SVM0201P (the Welcome to Advantis panel). Your program must be able to recognize this panel ID.

To access the programmable interface, send: /pi and an Enter keystroke.

NOTE: You can type /pi in uppercase or lowercase letters and send it from any of the input fields.

SVM0201PSYSTEM: xxxxxxxx DATE: 95/02/27TERMID: xxxxxxxx TIME: 15:19:38CUSTOMER ASSISTANCE: ENTER “NOTIFY” OR CALL nnnnnnnnnn--------------------------------------------------------------------------------

@@@ W E L C O M E T O @@ @@ @@ @ @@ @@ @@ @@@@ @@@@@ @@ @@ @@@@ @@@ @@ @@@@@@@ @@@ @@@ @@ @@ @@ @@ @@ @ @@ @@ @@ @ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @@ @@ @@ @@ @ @@ @@ @ @@@ @@ @@ @ @@ @@ @ @@ @ @@ @ @ @@ @@ @@ @@@ @@ @ @@ @@ @@ @@@ @@ @@ @@@

--------------------------------------------------------------------------------ACCOUNT... ________ USERID... ______ PASSWORD... Enter desired product or service, or press the HELP key (PF1) for assistance.

===>

Introducing the programmable interface 2-3

Panel SVMI001P (the Network Programmable Interface Request panel) is sent to your device.

All data you send from this panel goes to the programmable interface command inter-preter. See Chapter 3, “Writing your programmable interface” for further details.

Using a line-mode device If you connect to the network through a line-mode device other than SNA/S RJE, your device receives the following message:

NOTE: The programmable interface is designed for use by programs and is not intended for interactive use. However, you can display and use the programmable interface panels interactively for designing and testing programs. Because the passwords you type on the interface panels are visible, you should be careful to protect password confidentiality.

SVMI001P Programmable Interface Facility

Type the programmable interface request and press Enter.

===>PF1=Help F3=Exit F12=Cancel

WELCOME TO THE IBM INFORMATION SERVICES.SYSTEM: SYSTEM01 TERMID: TERMID01 91/09/20 11:20:34CUSTOMER ASSISTANCE: 800-123-4567

ENTER “HELP” FOR LOGON ASSISTANCE.

ENTER USERID ACCOUNT.===>


All data you enter in response to this message is sent to the programmable interface command interpreter. See Chapter 3, “Writing your programmable interface,” for further details.

Using an SNA/S RJE deviceIf you connect to the network with an SNA/S RJE device, you bypass the line-mode welcome message and send your request directly to the programmable interface.

To access the programmable interface, enter the VTAM LOGON command with the user data field containing the programmable interface request (/pi) followed by a semicolon.

After the semicolon, send the programmable interface commands, as described in Chapter 3‚ “Writing your programmable interface.” For example:

logon applid(),data(/pi;L a=acct,u=userid,p=pswd,ap=anappl)

NOTE: The Series/1 supplies the application ID of a service manager.


Chapter 3

Writing your programmable

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . interface

This chapter describes the syntax you need to use to automate access to the network using the programmable interface. It describes the interactions that must occur between you and the network, the commands and parameters (or keywords) that the network can accept, and the responses it returns. The interactions are illustrated separately for:

n Full-screen (LU 2) devicesn Line-mode (LU 1) devices

Some options are available for full-screen devices only. You can find further illustra-tions of all interactions, for both full-screen and line-mode devices, in Chapter 4‚ “Sample flows.”

For information on how to make the initial connection to the network and to the programmable interface, see Chapter 1, “Connecting to the network” and Chapter 2‚ “Introducing the programmable interface.”

Suggestions for programming to the interfaceThere are several PC software packages available to help you automate your access to the network through the use of the programmable interface. An example of such a package is Advantis Passport or the INPCS 3270. For more information, see the Related Books section.

Typically, such packages provide a programming environment for you to create your own customized program for terminal-host application interaction. An example of INPCS—Entry that specifically interacts with the network programmable interface is provided in Appendix D, “Example of INPCS—Entry logon,” and an example of Advantis Passport is provided in Appendix E‚ “Example of Advantis Passport logon.”


If you are creating your own program, you should program to the unique panel IDs and message IDs that can be sent to your program from the network. If a panel ID or message ID is available, you should always use it. Your program should scan for 8 consecutive characters (SVMxxxxx). The rest of the panels or messages are subject to change at any time.

Syntax for logging on for users with full-screen and line-mode devices

The programmable interface LOGON command follows. You can use uppercase or lowercase letters when coding commands. Also, the order of keywords within the command is not important. You can append only one command directly to the LOGON command, and they must be separated with a /.

LOGONACCOUNT=account,USERID=user ID,PASSWORD=password[,LANGUAGE=language ID][,NEWPASSWORD=new password][,VERIFYPASSWORD=verify password][,PROPAGATE={YES|NO}][,MESSAGESTATUS={YES|NO}]

where:

LOGONindicates this is a programmed logon and a user identification follows. You can abbreviate LOGON as L.

ACCOUNT=accountspecifies the user’s account ID. You can abbreviate account as a.

USERID=user IDspecifies the user’s user ID. You can abbreviate userid as u.

PASSWORD=passwordspecifies the user’s password. You can abbreviate password as p.

LANGUAGE=language IDspecifies the language used for the current session. This keyword is optional. It is the 2-character ISO language code. You can abbreviate language as Ln.

NOTE: If you are logging on with a fast path or generic user ID, you only need LOGON, ACCOUNT, and USERID. All other parameters except LANGUAGE are ignored.

Writing your programmable interface 3-3

If the language ID is not supported or is omitted, the default language is used. The default language is the language in the terminal profile. If the terminal profile does not specify a language, the language in the user’s profile is used as the default. If neither the terminal profile nor the user profile specify a language, the language used by the installation is taken as the default.

NEWPASSWORD=new passwordspecifies the user’s new password. This keyword is optional. You can abbreviate newpassword as np.

The password must meet the following rules:

• It must contain 5 to 8 characters.

• The first character must be alphabetic.

• Three of the 5 characters must be unique.

• It must be different from the user’s last three passwords.

• It cannot be the reserved words cancel, help, or exit, or their abbreviations can, hel, and exi.

VERIFYPASSWORD=verify passworddouble checks the new password. This is optional. You can use it in conjunction with newpassword to ensure that the user’s new password is entered correctly. You can abbreviate verifypassword as vp.

PROPAGATE={YES|NO}specifies if a new password is to be used for network products that support propagate, as well as for logging on. This is optional. You can abbreviate propagate as pg.

YESindicates that the new password is to be changed on each eligible application and in the user’s profile. You can abbreviate yes as y.

If you use propagate=yes, there is a delay of approximately 30 seconds while the request is processed.

NOindicates that only the network password is to be changed. You can abbre-viate no as n. This the default.

MESSAGESTATUS={YES|NO}indicates whether or not user message status information is to be provided. If you append messagestatus to the LOGON command and you log on successfully, the system displays one of the following messages:

• “SVMI158I The logon was successful. A new message has arrived.”


• “SVMI159I The logon was successful. There are messages.”

• “SVMI160I The logon was successful. There are no messages.”

You can abbreviate messagestatus as ms. This keyword is optional.

YESspecifies that the logon completion message is to include the status of user messages for the user. You can abbreviate yes as y.

NOspecifies that the logon completion message is not to include the status of user messages for the user. You can abbreviate no as n. This is the default.

LOGON examples

NOTE: If you specify messagestatus=y when logging on, the network ignores any commands, such as SELECT, appended to the LOGON command.

logon account=myaccnt,userid=myuser,password=mypswd

L a=myaccnt,u=myuser,p=mypswd

LOGON ACCOUNT=MYACCNT,USERID=MYUSER,PASSWORD=MYPSWD,LANGUAGE=US,NEWPASSWORD=NEWPASS,VERIFYPASSWORD=NEWPASS,PROPAGATE=YES

logon account=myaccnt,userid=myuser,password=mypswd,messagestatus=yes

logon a=myaccnt, u=*

logon a=myaccnt, u=genid


Syntax for selecting a single product for users with full-screen and line-mode devices

The SELECT command enables you to route a user to a single product. If you want a full-screen device user to be able to choose from more than one product, you can use the PRODUCTMENU command and provide the user with a selection menu. See “Syntax for displaying a product selection menu for users with full-screen devices” on page 3-6.

The format of the programmable interface SELECT command follows. You can use uppercase or lowercase letters when coding it. Also, the order of keywords within the command is not important. You can append the SELECT command directly to the LOGON command, separating the two commands with /, or you can send it by itself after you have sent LOGON and returned to the SVMI001P panel. For fast path and generic, APPLICATION is optional.

SELECTAPPLICATION=product[,RELEASE={YES|NO}][,LOGMODE=logmode][,USERDATA=user data]

where:

SELECTidentifies that a product is being requested. You can abbreviate SELECT as s.

APPLICATION=productspecifies the product you want to use. You can abbreviate application as ap.

RELEASE={YES|NO}specifies where you return when you finish using this product. This is optional. You can abbreviate release as r.

YESindicates that the session is released to VTAM or disconnected, depending on how your terminal is connected to the network. Leased connections are released to VTAM, while dial connections are dropped from the dial port (phone line is disconnected). You can abbreviate yes as y.

NOindicates that the user is returned to the Programmable Interface Request panel. You can abbreviate no as n. This is the default.

NOTE: The release keyword ensures that the LU-to-LU session terminates when you finish using a product.


LOGMODE=logmodespecifies the logmode you use for the session between the product and the terminal. This keyword is optional. The network uses the logmode you specify here unless the user’s profile specifies otherwise. You can abbreviate logmode as lm.

USERDATA=user datais free-format data that you can pass to the product. This keyword is optional. If you use it, this data is used for the application selected instead of the user data in the user profile.

Because this is a free-format field, you may use characters that are also used as delimiters such as /, comma, and blank. If you use any of these delimiters, you must enclose the entire string within apostrophes or quotation marks. If the string contains an apostrophe, enclose the string in quotation marks. If the string contains a quotation mark, enclose the string in apostrophes.

You can abbreviate userdata as ud.

SELECT examples

Syntax for displaying a product selection menu for users with full-screen devices

The programmable interface PRODUCTMENU command enables you to provide full-

NOTE: If you do not specify a logmode, the network uses the user’s profile if one exists or the terminal profile; the default is the VTAM logmode.

NOTE: This field is limited to 100 bytes maximum length.

select application=payroll

LOGON ACCOUNT=MYACCNT,USERID=MYUSER,PASSWORD=MYPSWD/SELECT APPLICATION=PAYROLL,LOGMODE=ALOGMODE,USERDATA=”data for the user’s payroll/wages package”

L a=myaccnt,u=myuser,p=mypswd/s ap=payroll,r=y


screen device users with a product selection menu. This command has no parameters or keywords. You can use uppercase or lowercase letters when coding it. You can send it with the LOGON command, separating the two commands with /, or you can send it by itself after you send LOGON and return to the SVMI001P panel. This command is for users with full-screen devices only.

PRODUCTMENU

where:

PRODUCTMENUindicates that you want to route the user to a product menu panel SVMI004P, where the user can select an application. You can abbreviate PRODUCTMENU as pm. For the fast path or generic user, pm is ignored.

PRODUCTMENU examples

Logging on and selecting a product or product menu for users with full-screen devices

This section describes how either to connect users with full-screen devices to one particular product or present them with a product selection menu so they can select a product themselves. To perform this task, use the syntax described in “Syntax for selecting a single product for users with full-screen and line-mode devices” on page 3-5 and “Syntax for displaying a product selection menu for users with full-screen devices” on page 3-6.

When bind processing is complete, the network sends panel SVM0201P. The panel illustrated here is the Welcome to Advantis panel. The panel you receive may have a different format, but the first data on your panel is always the panel identification, SVM0201P. The cursor is always positioned in an input field that is capable of accepting the programmable interface command, /pi.

NOTE: When the system displays the Network Product Selection panel, the session is no longer under the control of the programmable interface. The user is in interactive mode.

LOGON ACCOUNT=MYACCNT,USERID=MYUSER,PASSWORD=MYPSWD/PRODUCTMENU

L a=myaccnt,u=myuser,p=mypswd/pm


To access the programmable interface, request the SVMI001P panel from the network by sending /pi and an Enter keystroke.

When you run the program, the network responds to this request by sending panel SVMI001P. The cursor is positioned at the start of a 432-byte input field.

A period at row 11, column 74 marks the end of the input field.

To log on a user to the network, send a LOGON command and an Enter keystroke.

When you run the program, the network responds to this command by sending panel


@@@ W E L C O M E T O @@ @@ @@ @ @@ @@ @@ @@@@ @@@@@ @@ @@ @@@@ @@@ @@ @@@@@@@ @@@ @@@ @@ @@ @@ @@ @@ @ @@ @@ @@ @ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @@ @@ @@ @@ @ @@ @@ @ @@@ @@ @@ @ @@ @@ @ @@ @ @@ @ @ @@ @@ @@ @@@ @@ @ @@ @@ @@ @@@ @@ @@ @@@


===>

SVMI001P Programmable Interface Request Panel

Type the Programmable Interface request and press Enter.



SVMI002P. If the logon is successful, panel SVMI002P contains the message “SVMI100I The logon was successful.”

If your LOGON command is incorrect, or if an error occurs while the network is attempting to execute the command, panel SVMI002P contains the command you sent and an appropriate error message.

You can send a SELECT or PRODUCTMENU command with the LOGON command, separating the commands with /. However, the LOGON command must complete successfully before the network can process any appended command. If you append a command to the LOGON command and an error occurs in the logon, the network ignores the appended command.

SVMI002P Programmable Interface Response Panel

Press ENTER to continue.

LOGON A=MYACCT,U=MYUSER,P=MYPSWD/SELECT AP=PAYROLL,R=Y

SVMI112E THE PASSWORD HAS EXPIRED.

===>


Select one option from the following table.

Syntax for browsing messages for users with full-screen devices

The MESSAGE command allows users with full-screen devices to browse their messages. You can use uppercase or lowercase letters when coding the MESSAGE command. It can be appended directly to the LOGON command if you separate the two commands with a /. The order of the keywords within the command is not important. This command has the following format.

MESSAGE[VIEWALL={YES|NO}][,RETURN={YES|NO}]

where:

MESSAGE specifies that the Network Message panel, SVMI010P, is being requested to enable the user to browse user messages. You can abbreviate MESSAGE as m.

If you: The network:

Append a SELECT command to LOGON, send the commands, and the network processes them successfully

Passes the session to the application product you specified.

Append a PRODUCTMENU command to LOGON, send the commands, and the network processes them successfully

Displays Network Product Selection panel, SVMI004P.

Run a successful LOGON command without any appended command

Returns SVMI002P with a successful logon message. (Send an Enter keystroke, and the system returns panel SVMI001P and reads the next part of your code. For example, you might send a SELECT command and an Enter keystroke or a PRODUCTMENU command and an Enter keystroke.)

Run a LOGON command with SELECT or PRODUCTMENU appended to it, and one of the commands does not complete successfully

Sends panel SVMI002P. This panel contains the unsuccessful command and an appropriate error message.


VIEWALL={YES|NO}specifies which user messages the network displays. This is optional. You can abbreviate viewall as va.

YESindicates that the network displays all user messages, including those the user has already viewed. You can abbreviate yes as y.

NOindicates that the network displays only new user messages. You can abbre-viate no as n. This is the default.

RETURN={YES|NO}specifies the disposition of the session when returning from the Network Message panel. This is optional. You can abbreviate return as rn.

YESindicates that the user returns to the Programmable Interface Request panel, SVMI001P, after exiting the message receiving panel. You can abbreviate yes as y. This is the default.

NOindicates that the user passes to the product selection menu upon exiting the Network Message panel. You can abbreviate no as n.

MESSAGE examples

Logging on and enabling users with full-screen devices to browse user messages

This section describes how to enable users to browse user messages from the command input panel using a full-screen device. This procedure requires the LOGON command’s messagestatus keyword and the MESSAGE command.

NOTE: When the system displays the message receiving panel, the user is in interactive mode for the purpose of browsing messages.

LOGON ACCOUNT=MYACCNT,USERID=MYUSER,PASSWORD=MYPSWD/MESSAGE VIEWALL=YES

L a=myaccnt,u=myuser,p=mypswd/m rn=n


To log on a user, find out whether new user messages have arrived, and enable the user to browse any new messages, follow these steps:

1 To access the programmable interface, send: /pi and an Enter keystroke.

2 To log on the user so the system displays the status of the user’s messages, send the LOGON command with messagestatus set to yes.

For example, send: L a=abcd,u=user,p=pswd,ms=y and an Enter keystroke.

When you run the program, the network responds by displaying the SVMI002P panel.

NOTE: The network ignores other commands appended to LOGON when you specify messagestatus=y, including MESSAGE.


Press ENTER to continue.

SVMI1581 THE LOGON WAS SUCCESSFUL. A NEW MESSAGE HAS ARRIVED.


One of the following occurs:

3 To display SVMI001P, the network Programmable Interface Request panel, send an Enter keystroke.

The network responds with panel SVMI001P and reads the next command in your program.

If:The network displays this message:

A new user message has arrived that the user has not seen

“The logon was successful. A new message has arrived.”

There are user messages that the user has viewed but that have not yet expired

“The logon was successful. There are messages.”

The user has no user messages “The logon was successful. There are no messages.”





4 Refer to the following table to determine which command to send.

Getting help with a full-screen deviceIf a terminal user accidentally invokes the programmable interface, the network displays panel SVMI001P.

To get help, the user can either press F1 or:

1 On the command line, type: help

2 Press Enter.

3 Press F3 to exit.

If you want to do this:

Send this command:

When you run the program, the network:

Display SVM4501P, the Network Message panel

MESSAGE Displays SVM4501P with the new user message or messages. Users must press F3 to return to either the program-mable interface or the product selection menu after viewing user messages, depending on how you set up the MESSAGE command. See “Syntax for browsing messages for users with full-screen devices” on page 3-10.

To return to SVMI001P, send: end

Display SVMI004P, the Product Selection panel

PRODUCTMENU Displays SVMI004P. The user can select a product from the menu. See “Syntax for displaying a product selection menu for users with full-screen devices” on page 3-6.

Select a product for a user

SELECT Passes the session to the application product you indicate with the APPLI-CATION keyword. See “Logging on and selecting a product for users with line-mode devices” on page 3-15.


The network displays the Network Programmable Interface Help panel, SHPG9USD.

Logging on and selecting a product for users with line-mode devices

This section describes how to connect users with line-mode devices to the product they select. The procedure for users with SNA/S RJE devices is slightly different; for an example, see “Using an SNA/S RJE device” on page 2-4.

When bind processing is complete, the network sends the line-mode welcome message, SVM0201L.

To access the programmable interface, send: /pi and an Enter keystroke.

SHPG9USD Programmable Interface Help

You have accessed the programmable interface facility.

You use the programmable interface facility to allowprogrammable devices to automate the logon, product selection,and logoff processes.

This facility is meant for use by programs. It is not intendedfor interactive use by a person.

To return to the logo panel, press F3, or type Exit and pressENTER.

PF3=End

===>





When you run the program, the network responds by sending the line-mode command prompt, SVMI001L. This indicates that the programmable interface is active.

To log on to the network, send a LOGON command. You can enter a maximum of 432 bytes.

If your LOGON command is incorrect, or if an error occurs while the network attempts to execute the command, the network returns an appropriate error message followed by the line-mode command prompt, SVMI001L. Run the LOGON command again.

If your LOGON command is successful, the network reads the next command; for example, the SELECT command.

The remaining paths are similar to those used with a full-screen interface, as described in “Logging on and selecting a product or product menu for users with full-screen devices” on page 3-7. The difference is that the line-mode interface does not have a response message equivalent to the full-screen panel SVMI002P. This eliminates the need to send an Enter keystroke before the next command.

Getting HELP with a line-mode deviceIf a terminal user accidentally invokes the programmable interface, the network displays message SVMI001L.

To get help, the user can:

1 Type: help

2 Press Enter.

NOTE: You can send a SELECT command with the LOGON command, separating the two commands with /. However, the LOGON command must complete successfully before the network can process any other command. If you send a SELECT command with the LOGON command and an error occurs in the logon, the network ignores the SELECT command.

SVMI001L ENTER A COMMAND OR A REQUEST===>


The network displays message SHPI001L.

Syntax for logging off for users with full-screen and line-mode devices

The syntax of the LOGOFF command is:

LOGOFF[RELEASE={YES|NO}]

where:

LOGOFFindicates that the programmable interface session is to be terminated. You cannot abbreviate LOGOFF.

RELEASE={YES|NO}specifies where you return when you finish. This is optional. You can abbreviate release as r.

YESindicates that the session is released to VTAM or disconnected, depending on how your terminal is connected to the network. Leased-line connections are released to VTAM, while dial connections are dropped from the dial port (phone line is disconnected). You can abbreviate yes as y.

NOindicates that the user is returned to the Programmable Interface Request panel. You can abbreviate no as N. This is the default.

SHPI001L PROGRAMMABLE INTERFACE HELPYOU HAVE ACCESSED THE PROGRAMMABLE INTERFACE FACILITY.

YOU USE THE PROGRAMMABLE INTERFACE FACILITY TO ALLOW PROGRAMMABLEDEVICES TO AUTOMATE THE LOGON, PRODUCT SELECTION, AND LOGOFFPROCESSES.

THIS FACILITY IS MEANT FOR USE BY PROGRAMS. IT IS NOT INTENDEDFOR INTERACTIVE USE BY A PERSON.

TO RETURN TO THE WELCOME MESSAGE TYPE EXIT AND PRESS ENTER.

SVMI001L ENTER A COMMAND OR A REQUEST. ===>


LOGOFF examples

NOTE: The release keyword ensures that the programmable interface session terminates when you finish using a product. If a terminal’s profile tells it to return to VTAM after a session, this keyword has no effect.

LOGOFF

logoff r=y

LOGOFF RELEASE=YES


Chapter 4

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample flows

This chapter illustrates some typical interactions between your program and the network. Examples for full-screen (LU 2) devices are shown first, followed by the equivalent examples for line-mode (LU 1) devices.

Examples for full-screen devicesThis section contains sample flows for LU 2 devices only. Examples for line-mode devices are illustrated in “Examples for line-mode devices” on page 4-14.

Logging on, selecting a product, and logging off

From your program, the network reads: /pi and an Enter keystroke.


@@@ W E L C O M E T O @@ @@ @@ @ @@ @@ @@ @@@@ @@@@@ @@ @@ @@@@ @@@ @@ @@@@@@@ @@@ @@@ @@ @@ @@ @@ @@ @ @@ @@ @@ @ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @@ @@ @@ @@ @ @@ @@ @ @@@ @@ @@ @ @@ @@ @ @@ @ @@ @ @ @@ @@ @@ @@@ @@ @ @@ @@ @@ @@@ @@ @@ @@@


===>


The network responds by sending the following panel:

The network reads: L a=accnt1,u=johnd,p=secret1 and an Enter keystroke.

It responds:

The network reads another Enter keystroke.





Press Enter to continue.

SVMI1001 THE LOGON WAS SUCCESSFUL

Sample flows 4-3

It responds:

The network reads: s ap=payroll,r=y and an Enter keystroke.

It responds by establishing a session with the product Payroll for user ID JOHND.

You can send the SELECT command with the LOGON command, separating the commands with /. For example:

L a=accnt1,u=johnd,p=secret1/s ap=payroll,r=y

When you terminate the session with the product, the session is released to VTAM or disconnected, depending on how the terminal accesses the network (leased or dial) because r=y was specified. If you accessed the network through a leased line, the session is released to VTAM; if you accessed the network through a dial line, you are disconnected.





Logging on and changing a password



The network reads: L a=accnt1,u=johnd,p=secret1,np=jasb007,vp=jasb007,pg=y and an Enter keystroke.


@@@ W E L C O M E T O @@ @@ @@ @ @@ @@ @@ @@@@ @@@@@ @@ @@ @@@@ @@@ @@ @@@@@@@ @@@ @@@ @@ @@ @@ @@ @@ @ @@ @@ @@ @ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @@ @@ @@ @@ @ @@ @@ @ @@@ @@ @@ @ @@ @@ @ @@ @ @@ @ @ @@ @@ @@ @@@ @@ @ @@ @@ @@ @@@ @@ @@ @@@


===>




Sample flows 4-5

It responds:

The network reads an Enter keystroke.

It responds:

The network now can read another command; for example, SELECT or LOGOFF.

The password for user ID JOHND is changed to JASB007. Because you set password propagation to yes (pg=y), this password is applied to all eligible applications that user ID JOHND accesses on the network.



SVMI1001 THE LOGON WAS SUCCESSFUL





Logging on with MESSAGESTATUS=YES and displaying a product selection menu




@@@ W E L C O M E T O @@ @@ @@ @ @@ @@ @@ @@@@ @@@@@ @@ @@ @@@@ @@@ @@ @@@@@@@ @@@ @@@ @@ @@ @@ @@ @@ @ @@ @@ @@ @ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @@ @@ @@ @@ @ @@ @@ @ @@@ @@ @@ @ @@ @@ @ @@ @ @@ @ @ @@ @@ @@ @@@ @@ @ @@ @@ @@ @@@ @@ @@ @@@


===>




Sample flows 4-7

The network reads: L a=accnt1,u=johnd,p=jasb007,ms=y/pm and an Enter keystroke.

It responds:

Because there are no messages, it is unnecessary to view the message receiving panel. To access the SVMI001P panel, send an Enter keystroke.

NOTE: If you use messagestatus=yes, the network ignores any command that follows the LOGON command. In the previous example, the network ignores the PRODUCTMENU command. See “Syntax for selecting a single product for users with full-screen and line-mode devices” on page 3-5.



SVMI1001 THE LOGON WAS SUCCESSFUL. THERE ARE NO MESSAGES.


The network reads the keystroke and responds:

Because messagestatus was set to yes when you sent the LOGON command, the network ignored the PRODUCTMENU command originally appended to it. Send the PRODUCTMENU command separately from the LOGON command to access the product selection menu.

When you run the program, the network reads: PM and an Enter keystroke.

The network responds by displaying the panel, SVMI004P.




SVMI004P NETWORK PRODUCT SELECTION Page 1SYSTEM: SYSTEM01 DATE: 95/02/27TERMID: TERMID01 TIME: 15:20:25CUSTOMER ASSISTANCE: ENTER “NOTIFY” OR CALL 800-123-4567

PRODUCT DESCRIPTION ENTER “NOTIFY” OR CALL 1 MAILEXCH IBM MAIL EXCHANGE 800-123-4567 2 PAYROLL PAYROLL APPLICATION 555-PAY-HELP 3 VM VM SYSTEM 813-555-1234

Enter selection or press the END key before leaving this terminal unattended.

PF1=HELP PF3=END PF5=SERVICES

===>

Sample flows 4-9

The session exits the programmable interface at this point. The user is now in inter-active mode.

To choose the Payroll Application in this example, on the command line, the user can type 2 or PAYROLL and press Enter.

The network responds by establishing a session with the product Payroll for user ID JOHND.

When the user terminates a session with the product, one of the following occurs.

Recovering from an unsuccessful logon attempt


If you accessed the network The session

Through a leased line Returns to the Network Product Selection panel, SVMI004P.

Through a dial line Returns to the Advantis panel, SVM0201P.


@@@ W E L C O M E T O @@ @@ @@ @ @@ @@ @@ @@@@ @@@@@ @@ @@ @@@@ @@@ @@ @@@@@@@ @@@ @@@ @@ @@ @@ @@ @@ @ @@ @@ @@ @ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @@ @@ @@ @@ @ @@ @@ @ @@@ @@ @@ @ @@ @@ @ @@ @ @@ @ @ @@ @@ @@ @@@ @@ @ @@ @@ @@ @@@ @@ @@ @@@


===>



The network reads: L a=accnt1,u=johnd/s ap=mvsps and an Enter keystroke.

It responds:

The network reads an Enter keystroke.

NOTE: The password was omitted by the user.






L A=ACCNT1,U=JOHND/S AP=MVSPS

SVMI103E THE PASSWORD IS MISSING.

Sample flows 4-11

It responds:

The network reads: L a=accnt1,u=johnd,p=jasb007/s ap=mvsps and an Enter keystroke.

It responds by establishing a session with the product MVSPS for user ID JOHND.

Browsing messages






@@@ W E L C O M E T O @@ @@ @@ @ @@ @@ @@ @@@@ @@@@@ @@ @@ @@@@ @@@ @@ @@@@@@@ @@@ @@@ @@ @@ @@ @@ @@ @ @@ @@ @@ @ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@@ @@ @@ @@ @ @@ @@ @@ @@ @@ @ @@ @@ @@ @@ @@ @@ @@ @@ @@ @ @@ @@ @ @@@ @@ @@ @ @@ @@ @ @@ @ @@ @ @ @@ @@ @@ @@@ @@ @ @@ @@ @@ @@@ @@ @@ @@@


===>



The network reads: L a=accnt1,u=johnd,p=jasb007,ms=y and an Enter keystroke.

It responds:






SVMI1581 THE LOGON WAS SUCCESSFUL, A NEW MESSAGE HAS ARRIVED.

Sample flows 4-13

The network reads an Enter keystroke. It responds:

The network reads: m rn=y and an Enter keystroke.

It responds:

Press PF3, or on the command line, type end and press Enter.




SVM4501P MESSAGES Page 1

---------------------------- USER MESSAGES -------------------------

FROM ACC1.WATAH SENT 1995/02/27 10:01:00 LANGUAGE:XX

END OF MESSAGES

PF1=HELP PF3=END

===>


The network responds:

The network now can read another command, for example SELECT or PRODUCTMENU.

Examples for line-mode devicesThis section contains sample flows for line-mode devices. If you have an SNA/S RJE device, the logon is slightly different. See “Using an SNA/S RJE device” on page 2-4. Full-screen device examples are illustrated in “Examples for full-screen devices” on page 4-1.

Logging on, selecting a product, and logging off








The network displays the message “SVMI001L Enter a command or a request.”

Sample flows 4-15

The network then reads: L a=accnt1,u=johnd,p=secret1

The network reads: s ap=payroll,r=y

It responds by establishing a session with the payroll application for user ID JOHND.

You can send the SELECT command with the LOGON command, separating the commands with /. For example:

L a=accnt1,u=johnd,p=secret1/s ap=payroll,r=y

When the session is finished, the dial line is disconnected.

Logging on and changing a password


The network then reads:

L a=accnt1,u=johnd,p=secret1,np=jasb007,vp=jasb007,pg=y

The network now can read another command, for example, SELECT or LOGOFF.

The password for user ID JOHND is now changed to JASB007. Because you set password propagation to yes (pg=y), this password is applied to all eligible applica-tions that user ID JOHND accesses on the network.

It responds with the messages “SVMI100I The logon was successful. SVMI001L Enter a command or a request.”




The network responds by sending the message “SVMI001L Enter a command or a request.”

It responds with the messages “SVMI100I The logon was successful. SVMI001L Enter a command or a request.”


Recovering from an unsuccessful logon attempt


The network then reads: L a=accnt1,u=johnd/s ap=mvsps

The network then reads: L a=accnt1,u=johnd,p=jasb007/s ap=mvsps

It responds by establishing a session with the product MVSPS for user ID JOHND.

NOTE: The password was omitted by the user.




The network responds by sending the message “SVMI001L Enter a command or a request.”

The network responds with the messages “SVMI103E The password is missing. SVMI001L Enter a command or a request.”

Appendix

© Copyright Advantis 1995 A-1

A

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using direct logon

The network offers another method for ANTs to provide logon data as part of the command used to access the network. This method is called direct logon.

Syntax for direct logonThere are two ways to specify that you want to use direct logon:

n When you issue LOGON APPLID to VTAM, specify the direct logon commands in the data parameter.

n Pass the direct logon commands through another application in the CINIT userdata field.

The format of the direct logon command is a subset of the support provided by the programmable interface. The format is as follows (you can use uppercase or lowercase letters):

LOGON ACCOUNT=account,USERID=user ID,PASSWORD=password[,LANGUAGE=language ID]

/SELECTAPPLICATION=product[,RELEASE={YES|NO}]

where:

LOGONindicates that this is a programmed logon and that a user identification follows. You can abbreviate LOGON as L.

ACCOUNT=accountspecifies the user’s account ID. You can abbreviate account as a.

USERID=user ID

A-2 Automating Access to the Network

specifies the user’s user ID. You can abbreviate userid as u.

PASSWORD=passwordspecifies the user’s password. You can abbreviate password as p.

The password must meet the following rules:

• It must contain 5 to 8 characters.

• The first character must be alphabetic.

• Three of the 5 characters must be unique.

• It must be different from the user’s last three passwords.

• It cannot be the reserved words cancel, help, or exit, or their abbreviations can, hel, and exi.

LANGUAGE=language idspecifies the language used for the current session. This parameter is optional. It is the 2-character ISO language code. If the language ID you specify is not supported, the welcome panel is displayed again with an appropriate error message, and you must restart the logon procedure. You can abbreviate language as ln.

If you omit the language ID, a default language is used, as follows:

• For logon, the default is the language in the terminal profile.

• For product selection, the default is the language in the user’s profile.

/ (slash)is a delimiter, separating the SELECT command from the LOGON command.

SELECTidentifies that a product or service is being requested. You can abbreviate select as s.

APPLICATION=productspecifies the product or service you want to use. You can abbreviate application as ap.


YESindicates that the session is released to VTAM or disconnected, depending on the terminal profile. You can abbreviate yes as y.

Using direct logon A-3

NOindicates that the user is returned to the welcome panel, or to the product selection panel, depending on the device characteristics defined in the terminal profile. You can abbreviate no as n. This is the default.

Examples of direct logon format

Logging off after you use direct logonThe format of the LOGOFF command is:

LOGOFF[RELEASE={YES|NO}]

where:

LOGOFFindicates that this is a programmed logoff and the LU-to-LU session is to be terminated. You cannot abbreviate LOGOFF.


YESindicates that the session is released to VTAM or disconnected, depending on the terminal profile. You can abbreviate yes as y.

NOTE: The release keyword ensures that the LU-to-LU session terminates when you finish using a product. If a terminal is profiled to return to VTAM after a session, this keyword has no effect.

LOGON ACCOUNT=ACCNT,USERID=JOHND,PASSWORD=SECRET1/SELECTAPPLICATION=PAYROLL

L=accnt1,u=johnd,p=secret1/s ap=payroll,r=y

A-4 Automating Access to the Network

NOindicates that the user is returned to the welcome panel. You can abbreviate no as n. This is the default.

Examples of format for logging off

NOTE: The release keyword ensures that the LU-to-LU session terminates when you finish using a product. If a terminal is profiled to return to VTAM after a session, this keyword has no effect.

LOGOFF

logoff r=y

LOGOFF RELEASE=YES

Appendix

© Copyright Advantis 1995 B-1

B

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using batch logon

If you use Series/1 for BSC RJE, you must use batch logon. This appendix describes how to create a batch logon card from the information provided to you by the network.

Creating a batch logon cardBefore you can use batch logon, you must obtain an account ID, user ID, and password. You must also have a product on your user profile. A sample of this infor-mation for IBM’s JES product might look like the following:

n Account=acctn User ID=useraan Password=secret1n JES2 product=ps1jes2n Remote number=rmt44 (supplied by IBM)n Remote password=pwpwpw

With this information, you create a batch logon card. For example:

/*logon acct,useraa,secret1 /*select ps1jes2/*userdatarmt44,,pwpwpw

Using the batch logon interfaceThe batch logon interface is a facility that allows programmable devices to interact with the network in a consistent manner. The interface provides the following functions:

n Logon processing through the network that includes verification of account, user ID, and password, as well as password maintenance.

n Verification that any product you select is on your user profile.

n Isolation of the application LU name.

n Ability of product owners to control the use of their product by using product access and session limit.

B-2 Automating Access to the Network

n Passing of user data to the selected application. This user data can either be modified by a user, protected from the user, or a combination of both of these.

Before you can use the batch logon interface, you must have the following:

n An accountn A network user IDn A passwordn A product segment on the network user ID. The product segment must have the

appropriate LU name of the application.

The format of the batch logon request is:

/*LOGON account,userid,pswd/new pswd/verify new pswd/*SELECT product/*USERDATA userdata

where:

accountis the account you are registered to use.

useridis the user ID you are registered to use.

pswdis your current network password.

new pswdis a request to change your network password. This is optional.

verify new pswdis verification of the previous parameter. This is optional.

productis the name of the application you want to be passed to, as contained in your user profile.

userdatais any data you want to pass in the CDINIT. This data replaces any data in your user profile, except protected data. This is an optional parameter.

Appendix

© Copyright Advantis 1995 C-1

C

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TWX line-mode messages

The Service Manager transmits the EBCDIC logo to TWX line-mode logical units. The Series/1 converts the EBCDIC logo from EBCDIC to ASCII before transmitting the line-mode logo to an asynchronous line-mode terminal.

EBCDIC LOGO:

þ - blank (X’40’)1

N - New Line (X’15’)L

C - Carriage Return (X’OD’)R

X - XON (X’11’)O

FRAME:

1 NCþ LR1

2 NCþ LR1

3 NCWELCOMEþTOþTHEþIBMþINFORMATIONþSERVICES LR 1 1 1 1 1

4 NCSYSTEM:þxxxxxxxxþTERMID:þxxxxxxxxþyy/mm/ddþhh:mm:ss LR 1 1 1 1 1

5 NCCUSTOMERþASSISTANCE:þxxx-xxx-xxxx LR 1 1

6 NCþ LR1

NOTE: These symbols are used in the following diagram.

C-2 Automating Access to the Network

7 NCCENTERþ”HELP”þFORþLOGONþASSISTANCE LR 1 1 1 1

8 NCþ LR1

9 NCENTERþUSERIDþACCOUNT LR 1 1

10 NC===>þX LR 1O

ASCII LOGO:

þ - blank (X’20’)1

L - New Line (X’OA’)F

C - Carriage Return (X’OD’)R

X - XON (X’11’)O

Line:

1 LCþ FR1

2 LCþ FR1

3 LCWELCOMEþTOþTHEþIBMþINFORMATIONþSERVICES LR 1 1 1 1 1

4 LCSYSTEM:þxxxxxxxxþTERMID:þxxxxxxxxþyy/mm/ddþhh:mm:ss LR 1 1 1 1 1

5 LCCUSTOMERþASSISTANCE:þxxx-xxx-xxxx FR 1 1

6 LCþ FR1

7 LCCENTERþ”HELP”þFORþLOGONþASSISTANCE FR 1 1 1 1

8 LCþ FR1

NOTE: These symbols are used in the following diagram:

TWX line-mode messages C-3

9 LCENTERþUSERIDþACCOUNT FR 1 1

10 LC===>þX FR 1O

C-4 Automating Access to the Network

Appendix

© Copyright Advantis 1995 D-1

D

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Example of INPCS—Entry logon

The following example shows an INPCS—Entry logon script generated by the PCSBUILD utility program. It has five entries consisting of four lines each. Descrip-tions of these entries follow the example.

\\tbl 51 SVM0201P 1 /PI[ENTER] Activating programmable interface.2 SVMI001P 1 L A=accnt1,U=johnd,P=[say ENTER PW:][GETQ PW][PUT PW][ENTER] Logging on.3 SVMI100I 1 [ENTER]S AP=VMXA[ENTER] Logon was successful. Accessing application.4 ICH70001I 0 ~ Application VMXA successfully accessed.5 SVMI204E [ENTER]LOGOFF[ENTER] Requested application unavailable, try again later. \\etbl

ENTRY 1When the system detects panel SVM0201P (the Welcome to Advantis panel), the first entry activates the programmable interface.

ENTRY 2When panel SVMI001P (the Programmable Interface Request panel) is displayed, the second entry issues the user LOGON command. It also prompts the user for the password, then inserts this password into the logon data stream.

ENTRY 3The third entry is activated when LOGON is successful and the programmable interface has issued message SVMI100I.

In this example, the application VMXA is now selected.

ENTRY 4The fourth entry checks for logon to the application that the user selected; if the LOGON is successful, it exits the INPCS—Entry logon process. (In this example, a successful LOGON to application VMXA is indicated when the system issues

D-2 Automating Access to the Network

message ICH70001I.)

If the application that the user selects is unavailable, entry 5 detects this and takes these actions:

1 issues the appropriate LOGOFF command to exit the programmable interface.

2 issues an appropriate message to the user.

3 exits from the logon process.

Appendix

© Copyright Advantis 1995 E-1

E

Example of Advantis Passport

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . logon

The following example shows an Advantis password logon script generated by the script editor accessed through the Advantis Passport/DOS setup program. It has five entries consisting of four lines each. Descriptions of these entries follow the example.

\\tbl 51 SVM0201P 1 /PI[ENTER] Activating programmable interface.2 SVMI001P 1 L A=accnt1,U=johnd,P=[say ENTER PW:][GETQ PW] [PUT PW][ENTER] Logging on.3 SVMI100I 1 [ENTER]S AP=VMXA[ENTER] Logon was successful. Accessing application.4 ICH70001I 0 ~ Application VMXA successfully accessed.5 SVMI204E 0 [ENTER]LOGOFF[ENTER] Requested application unavailable, try again later. \\etbl

ENTRY 1When the system detects panel SVM0201P (the Welcome to Advantis panel), the first entry activates the programmable interface.

ENTRY 2When panel SVMI001P (the Programmable Interface Request panel) is displayed, the second entry issues the user LOGON command. It also prompts the user for the password, then inserts this password into the logon data stream.

ENTRY 3The third entry is activated when LOGON is successful and the programmable interface has issued message SVMI100I.

NOTE: For other Advantis Passport products, use the panels provided with the products.

E-2 Automating Access to the Network

In this example, the application VMXA is now selected.

ENTRY 4The fourth entry checks for LOGON to the application that the user selected; if the LOGON command is successful, it exits the Advantis Passport logon process.

In this example, successful logon to application VMXA is indicated when the system issues message ICH70001I.

ENTRY 5If the application that the user selects is unavailable, entry 5 detects this and takes these actions:

1 issues the appropriate LOGOFF command to exit the programmable interface.

2 issues an appropriate message to the user.

3 exits from the logon process.

Appendix

© Copyright Advantis 1995 F-1

F

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messages and codes

This appendix lists the messages and corresponding codes that you might encounter when using the network’s programmable interface. A brief explanation of each message is given, with a description of the action taken by the system. The action that you, as programmer, need to take is also given where appropriate.

Messages are divided into nine categories:

n USSMSG10 welcome messagesn 3708 welcome messagen IN Gateway enhanced full-screen (EFS) messagen General messages (SVMI0xxC)n Logon request messages (SVMI1xxC)n Application selection and logoff messages (SVMI2xxC)n Message Service request messages (SVMI3xxx)n Product Menu request messages (SVMI4xxx)n Messages generated by other functions

F-2 Automating Access to the Network

The following notes are applicable to all programmable interface error messages::

USSMSG10 welcome messagesTwo versions of this message are illustrated here; the first of these is being phased out. You can either program to both versions, or check with your marketing representative to see if the first message is still in use.

WELCOME TO THE IBM INFORMATION SERVICES, INFORMATION NETWORK TERMINAL-ID --------------------------------------------- PLEASE KEY IN A CHARACTER AND PRESS THE ‘ENTER’ KEY IBMX9YYY

The new USSMSG10 is shown below. Program to the first 8 characters; the text of the message is subject to change.

USSMSG10 Your terminal is connected to the IBM Information Network. To use the network, type any character and press ENTER. To disconnect, follow the operating instructions for your terminal. Terminal ID: IBMXXX99

NOTES:

1. The programmable interface uses a two-step process to handle requests. The first step is to parse or separate the input stream into individual request units and parameters. During this phase, any syntactical errors (errors involving the format of the request) are detected and reported. This means that no attempt is made to perform any function until the entire request is valid.

The second step is to sequentially execute the request units, as defined above. For example, if a second request, such as SELECT, is appended to the LOGON request, the processing sequence is always LOGON/SELECT. If an error is detected while attempting to execute a request unit, an error is reported for the failing request and the remaining request units are ignored. Any previous requests have successfully completed.

2. If a logon has not been completed, the session with the terminal ends after the expiration of the logon time-out interval.

3. If you are using the programmable interface from a full-screen device, the system displays a response screen until it receives an Enter. When it receives an Enter, the system displays the network Programmable Interface Request panel so you can send another request.

Messages and codes F-3

3708 welcome messageThis is the message you see when dialing into the 3708.

======IBM 3708===EC A78348======RID 3708-001 88-0000192==================== C6: IBM INFORMATION SERVICES, INFORMATION NETWORK 3270 EMULATION VERS 3.0 ACCESS THRU PORT ID : 07

ENTER TERMINAL TYPE:

IN Gateway enhanced full—screen (EFS) welcome message

This is the message you see when connecting to the IN Gateway.

==== IN GATEWAY ==== RELEASE xxxxxx ========== PORT XX ======================

A2: Type the number of your terminal: ===>

General messages (SVMI0xxC)

SVMI001L ENTER A COMMAND OR A REQUEST.

Explanation: This is the line-mode prompt for the programmable interface.

Response: Input the format of the programmable interface request or a command (such as HELP) and press Enter.

System Action: The network waits for a command or the request.

SVMI090E TOO MANY REQUESTS WERE ENTERED.

Explanation: The input received from the terminal contained more than two requests.

Response: Check the format of the programmable interface request verifying that only two requests were submitted. If the data stream contains only two requests, check for data that contains a slash (/) without being enclosed in apostrophes (‘) or quotes (“). Correct the input and retry the request.

System Action: The request is rejected. The network waits for the next request.


SVMI091E A USER MUST LOG ON PRIOR TO SELECTING AN APPLICATION.

Explanation: A SELECT request was received but no user was logged on.

Response: Send a valid LOGON for the user then resubmit the SELECT request.


SVMI092E AN INVALID COMMAND OR FUNCTION KEY WAS ENTERED.

Explanation: A command was received, but the command was not supported or an unsupported function key was pressed. (For line-mode devices, this message can also occur if the request was not known.)

Response: Check the spelling of the command (or request) and ensure the correct key was pressed. Correct the input and retry the request.


SVMI094E THE SYSTEM DOES NOT RECOGNIZE THE COMMAND(S).

Explanation: The request is not supported by the programmable interface.

Response: Check the spelling of the command. If using the abbreviated form, check that the correct abbreviation is used. (For line-mode devices, message SVMI092E will be received instead of SVMI094E.) Correct the input and retry the command.


SVMI095E DUPLICATE REQUEST WAS ENTERED.

Explanation: The data stream contained two requests that were the same.

Response: Check the input for a duplicate request. Correct the input and retry the request.


SVMI097E YOUR SYSTEM IS TEMPORARILY UNAVAILABLE. PLEASE TRY AGAIN LATER.

Explanation: The system is unable to establish a session at this time. Under distributed CMC, the application to which you are being passed is not available at this time.

Response: Wait five minutes, then reinitiate the session and retry the request. If the request continues to fail, contact Customer Assistance for aid in determining the cause of the problem.

System Action: The user’s request has been rejected and the terminal disconnected from the system.


SVMI098E A PRODUCTMENU(PM) KEYWORD IS UNKNOWN.

Explanation: A PRODUCTMENU request was received but one of the keywords supplied was not recognized.

Response: Correct the input and retry the request.


SVMI099E A SYSTEM ERROR HAS OCCURRED.

Explanation: An internal error has occurred in the programmable interface.

Response: Retry the request. If the error condition persists, contact network Customer Assistance.


Logon request messages (SVMI1xxC)

SVMI100I THE LOGON WAS SUCCESSFUL.

Explanation: The user logged on to the network successfully.

Response: Send the next request.

System Action: The network waits for the next request.

SVMI101E THE ACCOUNT ID IS MISSING.

Explanation: The request does not contain an account.

Response: Check the format of the programmable interface LOGON request and verify an account is provided. Correct the input and retry the request.


SVMI102E THE USER ID IS MISSING.

Explanation: The request does not contain a user ID.

Response: Check the format of the programmable interface LOGON request, and verify a user ID is provided. Correct the input and retry the request.



SVMI103E THE PASSWORD IS MISSING.

Explanation: The request does not contain a password.

Response: Check the format of the programmable interface LOGON request and verify a password is provided. Correct the input and retry the request.


SVMI104E THE NEW PASSWORD IS NOT VALID.

Explanation: A new password was specified, but is not acceptable to the network.

Response: Check the format of the new password and verify it conforms to rules for passwords.

n For standard passwords:

• It must be 5 to 8 characters long.

• It must contain 3 different characters.

• It must not be the same as your 3 previous passwords.

• It must begin with an alphabetic character.

• It must not be the word “cancel”, “can”, “exit”, “exi”, “help” or “hel”.

• For extended passwords:

• It must follow all standard password rules.

• It must contain at least one extended password character. Extended password characters are:

. ? ; ‘ “ ( ) : &

• It can begin with an extended password character.

Correct the input and retry the request.


SVMI105E THE NEWPASSWORD (NP) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The NEWPASSWORD keyword, or its abbreviation, was specified but no new password was provided.




SVMI106E THE NEW PASSWORD AND VERIFY PASSWORD ARE NOT THE SAME.

Explanation: The verify password did not match the new password.

Response: Ensure the value specified for the verify password is the same as the value specified for the new password. Correct the input and retry the request.


SVMI107E THE USER’S PROFILE DOES NOT EXIST.

Explanation: No network user profile could be found for the user.

Response: Check that the account and the user ID specified on the programmable interface request are correct. If they are correct, contact network Customer Assistance for additional assistance. If they are incorrect, correct the input and retry the request.


SVMI108E THIS USER ID IS ALREADY LOGGED ON.

Explanation: The user ID requesting the programmable interface is already in session with the network.

Response: The installation has specified that a user ID may have only one session with the network. The terminal user will have to end the existing session before another session with the network can be established.


SVMI109E LOGON NOT PERMITTED -- USER HAS REACHED LOGON MAXIMUM.

Explanation: The user ID requesting the programmable interface has exceeded the network logon maximum.

Response: The terminal user will have to determine why and where the user ID is logged on. Press Enter to return to the input panel.

System Action: The user’s request has been rejected. The network waits until Enter is received. (The network terminates or disconnects the session with the terminal unless Enter is received before the time-out interval has expired.)


SVMI110E THIS USER ID IS NOT DEFINED TO THE SECURITY SYSTEM.

Explanation: The user ID entered in the programmable interface request is not enrolled to the network security system.

Response: The terminal user will have to determine why the user ID is not defined to the network security system. Contact network Customer Assistance for additional assistance.


SVMI111E THIS PASSWORD IS NOT VALID.

Explanation: The password entered is not valid for the user ID.

Response: Correct the password and retry the request.


SVMI112E THE PASSWORD HAS EXPIRED.

Explanation: The user’s password has expired.

Response: Specify a new password and retry the LOGON request.


SVMI113E NEW PASSWORD NOT ACCEPTED.

Explanation: The new password does not conform to security guidelines.

Response: Send Enter to return to the input panel and correct the password. Keep in mind the restrictions on password length, duplication of previous passwords and valid password characters when selecting the new password.

System Action: The user’s request has been rejected. The network waits until Enter is received.

SVMI115E THE USER ID HAS BEEN REVOKED.

Explanation: This user’s authority to access the network has been revoked.

Response: The terminal user will have to contact their system administrator or network Customer Assistance so that the user ID can be resumed.



SVMI116E THIS USER MUST HAVE AN EXTENDED PASSWORD.

Explanation: The user is defined to the network as a user requiring an extended password, but the password supplied contains no extended characters.

Response: Ensure the password contains at least one extended character. (Valid extended characters are: . ? ; ‘ “ ( ) : & .) Correct the password and retry the request.


SVMI117E THE NEW PASSWORD MUST BE AN EXTENDED PASSWORD.

Explanation: The user is defined to the network as a user requiring an extended password. But the new password supplied contains no extended characters.

Response: Ensure the new password contains at least one extended character. (Valid extended characters are: . ? ; ‘ “ ( ) : & .) Correct the new password and retry the request.


SVMI118E THE PASSWORD CONTAINS AN INVALID EXTENDED CHARACTER.

Explanation: The password entered contains a character that is invalid to the security system.

Response: Ensure all the characters in the password are valid password characters. (Valid extended characters are: . ? ; ‘ “ ( ) : & .) Correct the password and retry the request.


SVMI119E THE NEW PASSWORD CONTAINS AN INVALID EXTENDED CHARACTER.

Explanation: The new password entered contains a character that is invalid to the security system.

Response: Ensure all the characters in the new password are valid password characters. (Valid extended characters are: . ? ; ‘ “ ( ) : & .) Correct the new password and retry the request.



SVMI120E THIS USER IS NOT AUTHORIZED FOR A DIAL CONNECTION TO THE NETWORK.

Explanation: The user attempted dial access to the network and is not authorized for dial access.

Response: The terminal user will have to contact network customer assistance to determine if dial access should be allowed.


SVMI121E THE USER IS NOT AUTHORIZED TO USE THIS TERMINAL.

Explanation: The user has attempted to access the network via a port or terminal to which they are not authorized.

Response: The terminal user will have to contact network customer assistance to determine whether access to the port or terminal should be granted.


SVMI122E THE GENERIC LOGON LIMIT HAS BEEN REACHED FOR THIS USER.

Explanation: An attempt was made to logon with a generic ID but the logon limit for that ID has been reached.

Response: Logon with another ID or wait for another user of that ID to logoff.

System Action: The user’s logon request is rejected.

SVMI123E THE USER HAS EXCEEDED THE MAXIMUM NUMBER OF LOGONS.

Explanation: The user has attempted to logon, but the maximum number of logons have been exceeded. The maximum number of times a user can be logged on to the network with the same user ID is defined by the installation.

Response: The terminal user must wait until one of the existing sessions is termi-nated before network access is granted.


SVMI124E A LOGON ERROR HAS OCCURRED FOR THIS USER ID.

Explanation: The security system detected an error during the logon process.

Response: The terminal user should contact network Customer Assistance to determine the cause of the failure.



SVMI125E THE REQUESTED LANGUAGE IS NOT AVAILABLE.

Explanation: The language specified with the LOGON request is not available.

Response: Change the language to a language available on the network and retry the request.


SVMI126E THE VALUE FOR THE PROPAGATE (PG) KEYWORD MUST BE YES|Y OR NO|N.

Explanation: The product password propagation keyword specified with the LOGON request is not equal to yes or no.



SVMI127E ANOTHER USER ID IS ALREADY LOGGED ON TO THIS TERMINAL.

Explanation: A LOGON has been requested but another user ID is already logged on the terminal.

Response: LOGOFF the current user, then LOGON the new user.


SVMI128E THIS USER ID IS NOT AUTHORIZED TO CHANGE THE PASSWORD.

Explanation: The network access authorization for this user does not allow password changes.

Response: The LOGON request must not contain any keywords associated with a password change. These keywords are NEWPASSWORD, VERIFYPASSWORD, and PROPAGATE. If the access authorization is incorrect, the user should contact network Customer Assistance for help. Otherwise, correct the input and retry the request.


SVMI129E PASSWORDS CANNOT BE CHANGED IN BACKUP MODE.

Explanation: The network access is currently being provided by a backup system. While in backup mode, changes to the network passwords are not allowed.

Response: The LOGON request must not contain any keywords associated with a password change. These keywords are NEWPASSWORD, VERIFYPASSWORD, and PROPAGATE. Correct the input and retry the request.



SVMI130E PASSWORD PROPAGATION IS NOT PERMITTED FOR AN IESC USER.

Explanation: The user has been defined to the network as an IESC user. IESC rules do not allow the password to be propagated to the application processors.

Response: The PROPAGATE keyword of the LOGON request must specify NO|N or may be omitted. Correct the input and retry the request.


SVMI131E THE LANGUAGE (LN) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The LANGUAGE keyword or its abbreviation was specified, but no language was provided.



SVMI132E THE LOGON DATA IS MISSING.

Explanation: A LOGON request was received without any LOGON keywords. The LOGON request requires the account ID, the user ID, and the password.



SVMI133E THE SELECT DATA IS MISSING.

Explanation: A SELECT request was received without any SELECT keywords. For a standard user logon, the APPLICATION keyword is required. For a fast path or generic user logon, at least one of the RELEASE, LOGMODE, or USERDATA keywords is required.



SVMI134E A LOGON KEYWORD IS UNKNOWN.

Explanation: A LOGON request was received but one of the keywords supplied was not recognized. Examine each keyword for the correct spelling or abbreviation and ensure the keyword(s) are applicable to LOGON.




SVMI135E THE ACCOUNT ID IS GREATER THAN THE MAXIMUM LENGTH.

Explanation: The account ID is more than 8 characters in length.



SVMI136E THE EQUAL SIGN IS MISSING FROM THE ACCOUNT (A) KEYWORD.

Explanation: The ACCOUNT keyword, or its abbreviation, was located, but the required equal sign was not found.



SVMI137E THE USER ID IS GREATER THAN THE MAXIMUM LENGTH.

Explanation: The user ID is more than 8 characters in length.



SVMI138E THE EQUAL SIGN IS MISSING FROM THE USER ID (U) KEYWORD.

Explanation: The USER ID keyword, or its abbreviation, was located, but the required equal sign was not found.



SVMI139E THE PASSWORD IS GREATER THAN THE MAXIMUM LENGTH.

Explanation: The password is more than 8 characters in length.




SVMI140E THE EQUAL SIGN IS MISSING FROM THE PASSWORD (P) KEYWORD.

Explanation: The PASSWORD keyword, or its abbreviation, was located, but the required equal sign was not found.



SVMI141E THE NEW PASSWORD IS GREATER THAN THE MAXIMUM LENGTH.

Explanation: The new password is more than 8 characters in length.



SVMI142E THE EQUAL SIGN IS MISSING FROM THE NEWPASSWORD (NP) KEYWORD.

Explanation: The NEWPASSWORD keyword, or its abbreviation, was located, but the required equal sign was not found.



SVMI143E THE REQUESTED LANGUAGE IS NOT VALID.

Explanation: The language must be two characters.



SVMI144E THE EQUAL SIGN IS MISSING FROM THE LANGUAGE (LN) KEYWORD.

Explanation: The LANGUAGE keyword, or its abbreviation, was located, but the required equal sign was not found.




SVMI145E THE PROPAGATE (PG) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The PROPAGATE keyword, or its abbreviation, was specified but no propagate value was provided.



SVMI146E THE EQUAL SIGN IS MISSING FROM THE PROPAGATE (PG) KEYWORD.

Explanation: The PROPAGATE keyword, or its abbreviation, was located, but the required equal sign was not found.



SVMI147E A VERIFY PASSWORD IS NOT ALLOWED WITHOUT A NEW PASSWORD.

Explanation: The LOGON request contained a verify password without including a new password. The verify password is used to validate the new password prior to changing the password.



SVMI148E THE VERIFYPASSWORD (VP) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The VERIFYPASSWORD keyword, or its abbreviation, was specified but no verify password was provided.



SVMI149E THE VERIFY PASSWORD IS GREATER THAN THE MAXIMUM LENGTH.

Explanation: The verify password is more than 8 characters in length.




SVMI150E THE EQUAL SIGN IS MISSING FROM THE VERIFYPASSWORD (VP) KEYWORD.

Explanation: The VERIFYPASSWORD keyword, or its abbreviation, was located, but the required equal sign was not found.



SVMI151E A PROPAGATE IS NOT ALLOWED WITHOUT A NEW PASSWORD.

Explanation: The LOGON request contained a propagate without including a new password. The propagate is used to distribute the new password to the application processors.



SVMI152E THE ACCOUNT (A) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The ACCOUNT keyword, or its abbreviation, was specified but no account was provided.



SVMI153E THE USER ID (U) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The USER ID keyword, or its abbreviation, was specified but no user ID was provided.



SVMI154E THE PASSWORD (P) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The PASSWORD keyword, or its abbreviation, was specified but no password was provided.




SVMI155E THE VALUE FOR THE MESSAGESTATUS (MS) KEYWORD MUST BE YES|Y OR NO|N.

Explanation: The MESSAGESTATUS keyword specified with the LOGON request is not equal to yes or no.



SVMI156E THE EQUAL SIGN IS MISSING FROM THE MESSAGESTATUS (MS) KEYWORD.

Explanation: The MESSAGESTATUS keyword, or its abbreviation, was located, but the required equal sign was not found.



SVMI157E THE MESSAGESTATUS (MS) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The MESSAGESTATUS keyword, or its abbreviation, was specified but no value was provided.



SVMI158I THE LOGON WAS SUCCESSFUL. A NEW MESSAGE HAS ARRIVED.

Explanation: The user logged on to the network successfully. There are messages that the user has not seen.



SVMI159I THE LOGON WAS SUCCESSFUL. THERE ARE MESSAGES.

Explanation: The user logged on to the network successfully. There are messages that the user has already seen.




SVMI160I THE LOGON WAS SUCCESSFUL. THERE ARE NO MESSAGES.

Explanation: The user logged on to the network successfully. There are no messages for the user.



Application selection and logoff messages (SVMI2xxC)

SVMI201E THE APPLICATION IS MISSING.

Explanation: The request does not contain an application.

Response: Check the format of the programmable interface SELECT request and verify an application is provided. Correct the input and retry the request.


SVMI202E THE APPLICATION IS NOT ON THE USER’S PROFILE.

Explanation: The user requested an application not defined on their network profile.

Response: Verify the application selected in the SELECT command is correct. If it is correct, the terminal user will have to contact network Customer Assistance to ensure the product has been properly profiled under the user’s network profile. Otherwise, correct the input and retry the request.


SVMI203E THIS USER IS NOT AUTHORIZED TO USE THIS APPLICATION.

Explanation: The user has attempted to access an application to which they have not been authorized.

Response: The terminal user will have to contact network Customer Assistance to obtain access to the application.



SVMI204E THE REQUESTED APPLICATION IS NOT AVAILABLE.

Explanation: The session between the terminal and the selected application product cannot be established.

Response: The terminal user will have to contact network Customer Assistance to determine why the session cannot be established.


SVMI205E THE APPLICATION IS UNAVAILABLE. RELEASE SESSION AND RETRY REQUEST.

Explanation: The session between the terminal and the selected application product cannot be established.

Response: Issue a LOGOFF request with RELEASE equal to yes. This will release the session to VTAM or disconnect the session, depending on how the terminal is profiled to the network. Reestablish a session with the network and retry your request. If this fails, the terminal user will have to contact network Customer Assistance to determine why the session cannot be established.


SVMI206E THE APPLICATION DOES NOT SUPPORT THIS TYPE OF TERMINAL.

Explanation: The user has attempted to access an application for which access from this type of device is not allowed.

Response: The terminal user may have to contact network Customer Assistance to determine why the application access was not allowed.


SVMI207E THE VALUE FOR THE RELEASE (R) KEYWORD MUST BE YES|Y OR NO|N.

Explanation: The RELEASE keyword specified with the SELECT or LOGOFF request is not equal to yes or no.




SVMI208E THE LOGMODE (LM) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The LOGMODE keyword, or its abbreviation, was specified but no logmode was provided.



SVMI209E THE USERDATA (UD) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The USERDATA keyword, or its abbreviation, was specified but no user data was provided.



SVMI210E THE APPLICATION IS GREATER THAN THE MAXIMUM LENGTH.

Explanation: The application is more than 8 characters in length.



SVMI211E THE EQUAL SIGN IS MISSING FROM THE APPLICATION (AP) KEYWORD.

Explanation: The APPLICATION keyword, or its abbreviation, was located, but the required equal sign was not found.



SVMI212E THE LOGMODE IS GREATER THAN THE MAXIMUM LENGTH.

Explanation: The logmode is more than 8 characters in length.




SVMI213E THE EQUAL SIGN IS MISSING FROM THE LOGMODE (LM) KEYWORD.

Explanation: The LOGMODE keyword, or its abbreviation, was located, but the required equal sign was not found.



SVMI214E THE USERDATA IS GREATER THAN THE MAXIMUM LENGTH.

Explanation: The userdata is more than 100 characters in length.



SVMI215E THE EQUAL SIGN IS MISSING FROM THE USERDATA (UD) KEYWORD.

Explanation: The USERDATA keyword, or its abbreviation, was located, but the required equal sign was not found.



SVMI216E THE RELEASE (R) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The RELEASE keyword, or its abbreviation, was specified but no release value was provided.



SVMI217E THE EQUAL SIGN IS MISSING FROM THE RELEASE (R) KEYWORD.

Explanation: The RELEASE keyword, or its abbreviation, was located, but the required equal sign was not found.




SVMI218E A SELECT KEYWORD IS UNKNOWN.

Explanation: A SELECT request was received but one of the keywords supplied was not recognized. Examine each keyword for the correct spelling or abbreviation and ensure the keyword(s) are applicable to SELECT.



SVMI219E THE APPLICATION (AP) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The application keyword or its abbreviation was specified, but no application was provided.



SVMI250E A LOGOFF KEYWORD IS UNKNOWN.

Explanation: A LOGOFF request was received but one of the keywords supplied was not recognized. Examine each keyword for the correct spelling or abbreviation, and ensure the keyword(s) are applicable to LOGOFF.



SVMI251E THE APPLICATION CANNOT BE ACCESSED THROUGH A DIAL CONNECTION.

Explanation: An attempt was made to access an application through a dial device but that application does not support dial users.

Response: Contact your Service Administrator if access to the device is required.

System Action: The user’s logon request is rejected.

Message Service request messages (SVMI3xxx)

SVMI301E A USER MUST LOG ON PRIOR TO REQUESTING THE MESSAGE (M) SERVICE.

Explanation: A MESSAGE request was received but no user was logged on.

Response: Send a valid LOGON for the user then resubmit the SELECT request.



SVMI302E A MESSAGE (M) KEYWORD IS UNKNOWN.

Explanation: A MESSAGE request was received but one of the keywords supplied was not recognized.



SVMI303E THE VALUE FOR THE RETURN (RN) KEYWORD MUST BE YES|Y OR NO|N.

Explanation: The RETURN keyword specified with the MESSAGE request is not equal to yes or no.



SVMI304E THE VALUE FOR THE VIEWALL (VA) KEYWORD MUST BE YES|Y OR NO|N.

Explanation: The VIEWALL keyword specified with the MESSAGE request is not equal to yes or no.



SVMI305E THE EQUAL SIGN IS MISSING FROM THE RETURN (RN) KEYWORD.

Explanation: The RETURN keyword, or its abbreviation, was located, but the required equal sign was not found.



SVMI306E THE EQUAL SIGN IS MISSING FROM THE VIEWALL (VA) KEYWORD.

Explanation: The VIEWALL keyword, or its abbreviation, was located, but the required equal sign was not found.




SVMI307E THE RETURN (RN) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The RETURN keyword, or its abbreviation, was specified but no value was provided.



SVMI308E THE VIEWALL (VA) KEYWORD WAS SPECIFIED WITHOUT A VALUE.

Explanation: The VIEWALL keyword, or its abbreviation, was specified but no verify password was provided.



SVMI309E THE MESSAGE (M) SERVICE IS ONLY AVAILABLE FROM FULL-SCREEN DEVICES.

Explanation: A MESSAGE request was received from a line-mode device.

Response: The terminal user must use a full-screen device to access the MESSAGE

service through programmable interface.


Product Menu request messages (SVMI4xxx)

SVMI401E A USER MUST LOG ON PRIOR TO REQUESTING THE PRODUCTMENU (PM) SERVICE.

Explanation: A PRODUCTMENU request was received but no user was logged on.

Response: Send a valid LOGON for the user and then resubmit the PRODUCTMENU request.


SVMI402E PRODUCTMENU (PM) IS ONLY AVAILABLE FROM FULL-SCREEN DEVICES.

Explanation: A PRODUCTMENU request was received from a line-mode device.

Response: The terminal user must use a full-screen device to access the PRODUCTMENU service through programmable interface.

System Action: The request was rejected. The network waits for the next request.


Messages generated by other functions

SMGM001E THIS DEVICE IS NOT DEFINED TO THE NETWORK. CONTACT YOUR SERVICE ADMINISTRATOR.

Explanation: A terminal device type entry does not exist for this type of terminal.

System Action: No logo is displayed. After the time-out interval expires, the session is terminated.

Response: Contact your service administrator to determine if the terminal type you are using is supported by the network.

SMGM002E THIS TERMINAL IS NOT DEFINED TO THE NETWORK. CONTACT YOUR SERVICE ADMINISTRATOR.

Explanation: A terminal profile does not exist for this terminal.

System Action: No logo is displayed. After the time-out interval expires, the session is terminated.

Response: Contact your service administrator to determine if the terminal needs to be registered to the network.

© Copyright Advantis 1995 X-1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Glossary

This glossary defines words as they are used in this book. It includes terms and definitions from the IBM Dictionary of Computing (New York:McGraw-Hill, 1994). If you are looking for a term and cannot find it here, see the Dictionary of Computing for additional definitions.

Aaccess authority. The level of authority that a user requests for a type of access to data.

account. A unique identifier assigned to a group of users.

account ID. A name that identifies an account to a program, device, or system.

Advantis network. The Advantis communi-cations network that provides products and services to customers in the United States.

alphanumeric. Generally, any keyboard character, but for practical purposes should be restricted to alphabetic, numeric, space, and common punctuation characters.

American National Standard Code for Infor-mation Interchange (ASCII). The standard code, using a coded character set consisting of 7-bit coded characters (8 bits including parity check), used for information interchange among data processing systems, data communication systems, and associated equipment. The ASCII

set consists of control characters and graphic characters.

ANT. See attached network terminal.

application. A program that is written specif-ically for a user's work, such as a program that does payroll or inventory control.

archive. A place to store messages on a database for future reference.

ASCII. See American National Standard Code for Information Interchange.

asynchronous. A process that might have to wait in a processing queue before it is completed (unlike a synchronous process, which is completed within a regular or predictable time frame).

attached network terminal(ANT). A display terminal that communicates with the network by way of another network.

attachment testing. A test that is done to ensure that any device connected to a network can communicate over the network.

B

browse. To view a file on your terminal screen without changing it.

X-2 Automating Access to the Network

buffer. An area of storage that is temporarily reserved for use in performing an input/output operation into which data is read or from which data is written.

CCICS. See Customer Information Control System.

Customer Information Control System (CICS). A program that enables transactions entered at remote terminals to be processed at the same time.

Ddatabase. A collection of data stored together to serve one or more applications. Each database contains a related set of information. For example, one database might contain inventory data and another database might contain payroll data.

direct logon. Automates the logon process by freeing users from interacting directly with logon panels before they access the target appli-cation.

Disk Operator System (DOS). An operating system for computer systems that use disks and diskettes for auxiliary storage of programs and data.

DOS. See Disk Operating System.

EEBCDIC. Extended Binary-Coded Decimal Interchange Code. A coded character set consisting of 8-bit coded characters.

HHPO. See High Performance Option.

High Performance Option (HPO). An asynchronous data communications program that can provide fast access to the network rmation network from your personal computer.

IIBM Information Network. The IBM communications network that provides products and services to customers outside the United States.

Information Exchange. A communication service that allows users to send and receive information electronically.

IBM Information Network Personal Connec-tivity Service (INPCS). An asynchronous data communications program that can provide fast access to the IBM Information Network from your personal computer.

INPCS. See IBM Information Network Personal Connectivity Service.

JJCL. See Job Control Language.

JES. See Job Entry Subsystem.

Job Control Language. A language that identifies a job to an operating system and describes the job's requirements.

Job Entry Subsystem. A system facility for spooling, job queuing, and managing input/output.

Glossary X-3

Llogmode. Specifies the type of session to be used between the product and the terminal.

log off. The procedure by which a user discon-nects from a terminal session.

log on. The procedure by which a user initiates a session.

logical unit (LU). The unit used for processing, for example, LU 1 and LU 2.

LU-to-LU session. In SNA, a session between two logical units (LUs) in an SNA network. It provides communication between two end users or between an end user and an LU services component.

LU. See logical unit.

N NAT. See network-attached terminal.

network-attached terminal. Leased or dial-type terminal attached directly to the network. nickname

Ppanel. (1) A screen that displays a set of infor-mation: for example, a menu, a data entry panel, or a selection list. (2) A screen that displays information stored in the computer. A panel can display a menu, a set of data entry areas, or a selection list.

password. A combination of characters you enter when you log on, designed to be secret and to prevent unauthorized access to your data.

RRACF. See Resource Access Control Facility.

Resource Access Control Facility (RACF). An external security facility that enables you to control the security of your virtual machine. You can give users access to your minidisks and set the password for your user ID.

remote job entry (RJE). To submit a series of commands through a terminal or processor that has access to a computer through a data link.

RJE. See remote job entry.

SSDLC. See synchronous data link control.

secondary logical unit (SLU). In SNA, the logical unit (LU) that contains the secondary half-session for a particular LU-to-LU session.

SLU. See secondary logical unit.

SNA. See systems network architecture.

synchronous data link control (SDLC). A way to manage the synchronous, code-trans-parent, serial-to-bit transfer of information over a link connection.

syntax. The rules for constructing a command.

system ID. The name assigned to identify a system.

systems network architecture (SNA). The layered transparent protocols, formats, and operational sequences for transmitting infor-mation through network services and facilities.


UUCS. See Uniform Communication Standard.

United Nations/Trade Data Interchange (UN/TDI). An electronic data interchange standard for administration, commerce, and transpor-tation fields, developed by the United Nations Economic Commission for Europe.

Uniform Communication Standard (UCS).A standard EDI format used in the grocery industry.

UN/TDI. See United Nations /Trade Data Interchange.

user ID. A name that identifies a user to the network.

Wwindow. A portion of the screen set aside for a particular task or function.

© Copyright Advantis 1995 X-5

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index

Aabbreviations defined 1-9accessing

programmable interfaceusing full-screen device 2-2using line-mode device 2-3using SNA/S RJE device 2-4

acronyms defined 1-9at 1-6attached network terminal

connecting to the network 1-2general discussion 1-2

Bbatch logon

creating a batch logon card B-1interface

format B-1function B-1requirements B-1

browsing messagesformat examples 3-11syntax 3-10

Ccodes and messages

for application selection (SVMI2xxC) F-18for message service request (SVMI3xxx)

F-22for product menu request (SVMI4xxx)

F-24general (SVMI0xxC) F-3general discussion F-1generated by other functions F-25logoff (SVMI2xxC) F-18logon request (SVMI1xxC) F-5welcome messages

3708 F-3IN Gateway enhanced full screen F-3USSMSG10 F-2

connecting3708

SS/EFS to 3708 1-8attached network terminal

general discussion 1-2IN Gateway

HPO to the IN Gateway 1-9SS/EFS to the IN Gateway 1-8

network attached terminalgeneral discussion 1-2

network control program3270 to NCP-dial 1-43270 to NCP-leased 1-3

Series/1BSC 3275 to Series/1 1-7BSC RJE to Series/1 1-7

Series/1 or IN GatewaySNA/A to Series/1 for INPCS-Entry or

the IN Gateway 1-5SNA/S 3270 full-screen to Series/1 or

the IN Gateway 1-6SNA/S RJE to Series/1 or the IN Gate-

way 1-6


SNA/S SNUF to Series/1 or the IN Gate-way 1-6

SS/ELM to Series/1 or the IN Gateway 1-5

Ddial-up connections

3270 to NCP 1-4BSC 3275 to Series/1 1-7BSC RJE to Series/1 1-7HPO to the IN Gateway 1-9SNA/A to Series/1 for INPCS-Entry or the

IN Gateway 1-5SNA/S 3270 full-screen to Series/1 or the IN

Gateway 1-6SNA/S RJE to Series/1 or the IN Gateway

1-6SNA/S SNUF to Series/1 or the IN Gateway

1-6SS/EFS to 3708 1-8SS/EFS to the IN Gateway 1-8SS/ELM to Series/1 or the IN Gateway 1-5

direct logongeneral discussion A-1using

syntax A-1

EEBCDIC logo conversion C-1

IINPCS-Entry logon example D-1

Lleased-line connection

3270 to NCP 1-3logoff

directformat examples A-4

logonbatch

creating a card B-1using the interface B-1

directformat examples A-3syntax A-1

Mmessages and codes

application selection (SVMI2xxC) F-18general (SVMI0xxC) F-3general discussion F-1generated by other functions F-25IN Gateway enhanced full screen F-3logoff (SVMI2xxC) F-18logon request (SVMI1xxC) F-5message service request (SVMI3xxx) F-22product menu request (SVMI4xxx) F-24welcome messages


Nnetwork attached terminal

connecting to the network 1-1dial up

3270 to NCP-dial 1-4BSC 3275 to Series/1 1-7BSC RJE to Series/1 1-7HPO to the IN Gateway 1-9SNA/A to Series/1 for INPCS-Entry or

the IN Gateway 1-5SNA/S 3270 full-screen to Series/1 or

the IN Gateway 1-6SNA/S RJE to Series/1 or the IN Gate-

way 1-6SNA/S SNUF to Series/1 or the IN Gate-

way 1-6SS/EFS to 3708 1-8

Index X-7

SS/EFS to the IN Gateway 1-8SS/ELM to Series/1 or the IN Gateway

1-5

Pprogramming suggestions 3-1

Wwelcome messages


Communicating Your Comments to Advantis


GC34-2200-02

If you especially like or dislike anything about this book, please use one of the methods listed below to send your comments to Advantis. Whichever method you choose, make sure you send your name, address, and telephone number if you would like a reply.

Feel free to comment on specific errors or omissions, accuracy, organization, subject matter, or completeness of this book. However, the comments you send should pertain to only the information in this manual and the way in which the information is presented. To request additional publications, or to ask questions or make comments about the functions of Advantis products or services, you should talk to your Advantis representative.

When you send comments to Advantis, you grant Advantis nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you.

n If you prefer to send comments by mail, use the readers’ comment form (RCF) at the back of this book. If you are mailing an RCF from a country other than the United States, place the RCF in a separate envelope and provide the correct post-age.

n If you prefer to send comments by FAX, use this number:

United States and Canada: 813+878-5475

n If you prefer to send comments electronically, use this network ID:

IBM Mail Exchange: USIB2PH9 at IBMMAIL

Please include the following in your note:

n Title and publication number of this book

n Page number or topic to which your comment applies.

Readers’ Comments - We’d Like to Hear from You


Publication No. GC34-2200-02

Thank you for your responses. May we contact you? Yes No

When you send comments to Advantis, you grant Advantis a nonexclusive right to useor distribute your comments in any way it believes appropriate without incurring anyobligation to you.

Name

Company or Organization

Phone No.

Address

Overall, how satisfied are you with the information in this book?

How satisfied are you that the information in this book is:

Please tell us how we can improve this book:

VerySatisfied Satisfied Neutral Dissatisfied

VeryDissatisfied

Overall Satisfaction

VerySatisfied Satisfied Neutral Dissatisfied

VeryDissatisfied

Accurate

Easy to findEasy to understand

Well organizedApplicable to your tasks

Complete

Readers’ Comments - We’d Like to Hear from YouGC34-2200-02

GC34-2200-02

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 358 SCHAUMBURG, IL

POSTAGE WILL BE PAID BY ADDRESSEE

AdvantisDepartment RD10PO BOX 20143Tampa FL 33633-0872

Fold and Tape Please do not staple Fold and Tape

Cut or FoldAlong Line

automating access to the networkglobalnetwork.support.att.com/att/advdisp.pdfchapter 1,...

Documents