C Ics Admin Guide

PN 00734
Connect:Direct OS/390
CICS Administration Guide
PN 00734
Connect:Direct OS/390
CICS Administration Guide
Version 4.4
Connect:Direct OS/390 CICS Administration Guide Version 4.4 First Edition This documentation was prepared to assist licensed users of the Connect:Direct OS/390 system (Sterling Commerce Software). The Sterling Commerce Software, the related documentation and the information and know-how it contains, is proprietary and confidential and constitutes valuable trade secrets of Sterling Commerce, Inc., its affiliated companies or its or their licensors (collectively Sterling Commerce), and may not be used for any unauthorized purpose or disclosed to others without the prior written permission of Sterling Commerce. The Sterling Commerce Software and the information and know-how it contains have been provided pursuant to a license agreement which contains prohibitions against and/or restrictions on its copying, modification and use. Duplication, in whole or in part, if and when permitted, shall bear this notice and the Sterling Commerce, Inc. copyright legend. Where any of the Sterling Commerce Software is used, duplicated or disclosed by or to the United States government or a government contractor or subcontractor subject to the FARs, it is provided with RESTRICTED RIGHTS as defined in Title 48 CFR 52.227-19. Further, as and when provided to any governmental entity, governmental contractor or subcontractor subject to DFARs, the Sterling Commerce Software is provided pursuant to the customary Sterling Commerce license, as described in Title 48 CFR 227-7202 with respect to commercial software and commercial software documentation. The Sterling Commerce Software and the related documentation are licensed either AS IS or with a limited warranty, as described in the Sterling Commerce license agreement. Other than any limited warranties provided, NO OTHER WARRANTY IS EXPRESSED AND NONE SHALL BE IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR USE OR FOR A PARTICULAR PURPOSE. The applicable Sterling Commerce entity reserves the right to revise this publication from time to time and to make changes in the content hereof without the obligation to notify any person or entity of such revisions or changes. References in this manual to Sterling Commerce products, programs, or services do not imply that Sterling Commerce intends to make these available in all countries in which Sterling Commerce operates. Printed in the United States of America. Copyright 1999, 2004. Sterling Commerce, Inc. All rights reserved. Connect:Direct and Connect:Enterprise are registered trademarks of Sterling Commerce. All Third Party Software names are trademarks or registered trademarks of their respective companies. All other brand or product names are trademarks or registered trademarks of their respective companies.
CD390CAG403
Contents
Preface
Chapter Overview ................................................................................................................. Connect:Direct OS/390 Documentation ............................................................................... Getting Support for Sterling Commerce Products ................................................................ vii viii ix
Chapter 1
About the CICS Interface

Introduction to the Administration System ........................................................................... Components of the CICS Interface ....................................................................................... Structure of the Administration System................................................................................ Administration Screen Features ............................................................................................ System and Data Fields.................................................................................................. PF Keys.......................................................................................................................... 1-1 1-2 1-3 1-3 1-3 1-4
Chapter 2
Accessing the Primary Menu

Using the Administration System ......................................................................................... Using the Primary Menu ....................................................................................................... Entry Fields.................................................................................................................... 2-1 2-1 2-2
Chapter 3
Maintaining Configuration Information

Configuration Categories ...................................................................................................... Control Record............................................................................................................... DTF Node Records ........................................................................................................ Understanding Subtasks ......................................................................................... Network Node Records.................................................................................................. Accessing the Administration Configuration Screen............................................................ Entry Fields.................................................................................................................... Updating the Control Record ................................................................................................ Entry Fields.................................................................................................................... Menu Options ................................................................................................................ 3-1 3-1 3-1 3-2 3-2 3-2 3-2 3-3 3-4 3-5
iv
Connect:Direct OS/390 CICS Administration Guide
Updating DTF Node Records................................................................................................ Entry Fields .................................................................................................................... Updating Network Node Records ......................................................................................... Entry Fields ....................................................................................................................
3-6 3-7 3-7 3-8
Chapter 4
Working with the Administration Interface

Using the Connect:Direct Administration Interface Screen.................................................. Entry Fields .................................................................................................................... System Fields ................................................................................................................. Operating the CICS Interface ................................................................................................ Monitor Transaction....................................................................................................... Interface Tasks ............................................................................................................... Interface Startup ............................................................................................................. Interface Subtask Management ...................................................................................... Interface Request Management...................................................................................... Interface VTAM Session................................................................................................ 4-1 4-2 4-2 4-2 4-3 4-3 4-3 4-4 4-4 4-4
Chapter 5
Viewing Node Status

Accessing the Node Status Screen ........................................................................................ Line Commands ............................................................................................................. System Fields ................................................................................................................. Viewing the Work Queue...................................................................................................... System Fields ................................................................................................................. 5-1 5-1 5-2 5-3 5-3
Chapter 6
Maintaining Signon Defaults

How Connect:Direct Uses Signon Defaults .......................................................................... Accessing the Signon Defaults Screen .................................................................................. Entry Fields .................................................................................................................... System Fields ................................................................................................................. 6-1 6-2 6-2 6-3
Chapter 7
Viewing User Status

Accessing the User Status Screen ......................................................................................... Options ........................................................................................................................... System Fields ................................................................................................................. 7-1 7-2 7-2
Chapter 8
Operational Considerations
Signing On to Multiple DTFs from a Single IUI .................................................................. Signing On to a Single DTF from Multiple IUI Facilities .................................................... Performing an Immediate or Uncontrolled Shutdown .......................................................... Restarting Task ABENDS..................................................................................................... Accessing Accounting and Logging Information ................................................................. 8-1 8-2 8-2 8-3 8-3
Contents
Using the Extended Submit Facility (ESF)........................................................................... Specifying Connect:Direct Signon Parameters..................................................................... Understanding Connect:Direct CICS Data Sets.................................................................... Connect:Direct DTF and CICS Data Sets...................................................................... Connect:Direct CICS Data Sets ..................................................................................... Temporary Data Set .......................................................................................................
8-4 8-4 8-4 8-4 8-5 8-5
Chapter 9
Using the Application Interface

Accessing the API Driver Screen.......................................................................................... Driver Fields .................................................................................................................. Using the CICS API Option.................................................................................................. Linking DMQ012 .......................................................................................................... 9-1 9-2 9-3 9-4
Appendix A Glossary Index
CICS Messages
vi
Preface
The Connect:Direct OS/390 CICS Administration Guide is for programmers and network operations staff who use the CICS interface to maintain Connect:Direct OS/390. This manual assumes knowledge of the IBM OS/390 operating system and CICS. If you are not familiar with the OS/390 operating system, refer to the IBM library of OS/390 manuals.
Chapter Overview
The Connect:Direct OS/390 CICS Administration Guide contains the following chapters:
! ! ! ! ! ! ! ! ! ! !
Chapter 1, About the CICS Interface, briefly describes the CICS Interface internal components. Chapter 2, Accessing the Primary Menu, describes the signon and signoff procedures and describes the primary options available. Chapter 3, Maintaining Configuration Information, describes how to maintain the control record, DTF node records, and network node records in the configuration file using the configuration screen. Chapter 4, Working with the Administration Interface, describes the interface control screen and the operations of the interface. Chapter 5, Viewing Node Status, describes the node status screen and how to control accessible nodes; it also describes the work queue display. Chapter 6, Maintaining Signon Defaults, describes the signon defaults screen and how to update user signon records. Chapter 7, Viewing User Status, describes the user status screen and how to monitor user status. Chapter 8, Operational Considerations, describes multiple signons, controlled shutdowns, logging information, mode operations, and data sets available. Chapter 9, Using the Application Interface, describes the driver screen and how to use the sample program. Appendix A, CICS Messages, contains messages that may occur during the use of Connect:Direct OS/390 administration screens. The Glossary introduces terms used throughout the book when describing Connect:Direct OS/390.
viii
Connect:Direct OS/390 Documentation

The Connect:Direct OS/390 documentation library consists of the following manuals. These manuals are available in PDF format on the documentation CD-ROM.
! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !
Connect:Direct OS/390 Installation Guide describes planning and installing Connect:Direct. Connect:Direct OS/390 Release Notes describes release features and last-minute product information. Connect:Direct OS/390 Sysplex Requester Facility Installation Guide describes planning and installing the Sysplex Requester Facility (SRF). Shipped with purchase of SRF option only. Connect:Direct OS/390 Users Guide describes how to use Connect:Direct commands to create and control Processes. Connect:Direct OS/390 Administration Guide describes Connect:Direct administrative and system maintenance tasks. Connect:Direct OS/390 Quick Reference is a handy reference of Connect:Direct OS/390 commands and parameters. Connect:Direct OS/390 Activity Reporting System Users Guide describes the Activity Reporting System (ARS). Connect:Direct Console Operators Guide describes how to manage Connect:Direct data transfer activities from the operator console. Connect:Direct Problem Isolation Guide explains how to correct errors encountered during Connect:Direct functions. Connect:Direct Event Services Support Users Guide describes the use and data format of the Event Services feature. Connect:Direct Spool Transfer Users Guide describes the use of the Connect:Direct Spool Transfer feature. Connect:Direct Process Statements Guide describes Process statements and provides examples of cross-platform Processes. Connect:Direct Process Concepts and Examples Guide provides an overview of Connect:Direct, describes the general structure and syntax rules for the Process language, and includes numerous examples. Connect:Direct OS/390 CICS Users Guide describes how to use Connect:Direct commands to create and control Processes through the Customer Information Control System (CICS) interface. Connect:Direct OS/390 CICS Administration Guide describes how to perform Connect:Direct administrative and system maintenance tasks through the CICS interface. Connect:Direct OS/390 DBCS Support Guide describes how Connect:Direct OS/390 supports Double-byte Character Set (DBCS) translation. Connect:Direct File Agent Configuration Guide describes how to configure File Agent, an application integration component which detects files in watched directories and submits a Process to Connect:Direct when a file is detected. Connect:Direct Compatibility and Connectivity Chart shows the currently supported versions and platforms of Connect:Direct and the compatible Connect:Direct versions.
Preface
ix
Getting Support for Sterling Commerce Products

Sterling Commerce provides intuitive technical products and superior Help and documentation to enable you to work independently. However, if you have a technical question regarding a Sterling Commerce product, use the Sterling Commerce Customer Support Web site. The Sterling Commerce Customer Support Web site at www.sterlingcommerce.com is the doorway to Web support, information, and tools. This Web site contains several informative links, including a solutions database, an issue tracking system, fix information, documentation, workshop information, contact information, sunset and retirement schedules, and ordering information. Refer to the Customer Support Reference Guide at www.sterlingcommerce.com/customer/tech_support.html for specific information on getting support for Sterling Commerce products.
Chapter 1
About the CICS Interface
The CICS Interface provides a number of components that enable users and applications to access, control, and transfer data across networks. The major components, as illustrated on page 1-2, include:
Component Interactive User Interface (IUI) Application Program Interface (API) Description Enables users to transfer files, initiate applications, and monitor activity in a user-friendly environment. Enables the IUI and CICS Administration to communicate to the Data Transmission Facility (DTF) through the session manager. The API interprets the commands, but it is the responsibility of the session manager to establish communication sessions and perform standard session management functions. Controls information distribution to other nodes in the network. In a Connect:Direct/Plex environment, the Connect:Direct/Manager and Connect:Direct/Servers form the DTF. Enables users to submit data for transmission even if the DTF is not active. Connect:Direct requests sent to an inactive node are routed to the sending Transmission Control Queue (TCQ) until the inactive node is initiated.
Data Transmission Facility (DTF) Extended Submit Feature (ESF) Mode
Introduction to the Administration System

The Administration System helps you configure and control the interface. The tasks you can perform while using this system include:
! ! ! ! ! !
Configuring Connect:Direct OS/390 to provide the appropriate functionality to your users while maintaining optimum performance Defining the characteristics of the Connect:Direct DTFs to which Connect:Direct OS/390 submits requests Activating and deactivating the Connect:Direct interface Activating and deactivating the interface with specific Connect:Direct DTFs Adding, modifying, and deleting default user signon characteristics Monitoring user activity and intervening if those activities compromise Connect:Direct or the CICS environment
The system guides you through a series of nested menus, prompts you for input, and performs the requested function. If errors occur during the processing of your request, the system informs you of the cause of the error and, in some cases, suggests remedial action.
1-2
Components of the CICS Interface

The Connect:Direct OS/390 installation offers an optional selection to use the CICS interface. The following figure illustrates a CICS implementation.
Config
Profile
Netmap
IUI
IUI
IUI
IUI
IUI
IUI
IUI
IUI
IUI
IUI
Process
CICS
Connect: Direct OS/390 CICS API
Event Restart
ESF Mode DTF Session Mgr DTF Session Mgr
Connect:Direct DTF Session Mgr DTF Session Mgr
DTF Session Mgr
Connect: Direct DTF API VTAM
TCQ
Connect: Direct DTF 1
Local and Cross Domain DTF Sessions
Local Node DTF Configuration ESF or Primary DTF Session
Multi-Session Cross Domain DTF Signon
Single Session Cross Domain DTF Signon
Interrupted Session Management
Chapter 1 / About the CICS Interface
1-3
Structure of the Administration System

The menu structure of the Administration System follows.
Primary Menu
Node Status
Interface Status
Signon Defaults
Configuration
User Status
Work Queue
Control Record
DTF Node Records
Network Node Records
By typing the correct data in the Administration menus and screens, you can perform the following tasks:
! ! ! ! ! ! ! !
Check and control user status (USER STATUS) Add, update, and delete user signon characteristics (SIGNON DEFAULTS) Activate and deactivate the Connect:Direct DTF-to-CICS Interface (INTERFACE) Monitor and control node status (NODE STATUS) Monitor and control the work queue (WORK QUEUE) Modify the global control parameters (CONTROL RECORD) Add, delete or modify any DTF node parameters (DTF NODE RECORDS) Add, delete or modify any network node configurations (NETWORK NODE RECORDS)
Administration Screen Features

The screens are based on the 24 X 80 (V X H) characters of a standard IBM 3270 Model 2 display.
System and Data Fields

Each screen in the administration system contains information fields of various widths and attributes for your data and for system-displayed data. Information fields that are for typed data, all variable data is highlighted. Required fields are highlighted and optional fields are not. Variable fields are underscored to indicate the size of the field. As you perform your administrative activities, several system fields (TIME, and MESSAGE) display with current information about your typed data, and are updated with system information and responses to your
1-4
requests. The 8-character TIME field contains the system time expressed as hours, minutes, and seconds (HH:MM:SS), and is displayed in the upper right corner of the screen. The 75-character MESSAGE field is displayed near the bottom of the screen. It contains the system messages associated with the success or failure of your administrative activities. CICS Interface messages use the prefix SCCS to distinguish them from non-CICS messages. The format is SCCSnnnI, where nnn is the number of the message. These messages are listed in the CICS Messages appendix.
PF Keys
Some menus have available programmable function (PF) keys for additional options and maneuvering through the menu hierarchy. These PF key assignments are displayed across the bottom two rows of the administration screens and function as follows:
Keys PF3 PF5 PF6 PF7 PF8 PF9 PF10 PF11 ENTER CLEAR Function Exits the current screen, and takes you to the previous screen Adds an entry to the list on the screen Deletes an entry from the list on the screen Scrolls backward through the list of available data on the screen Scrolls forward through the list of available data on the screen Applies updates to screen information Scrolls to the left on the screen Scrolls to the right on the screen Refreshes screen data or processes a line command Resets the data on the screen to default values
Chapter 2
Accessing the Primary Menu
This chapter describes the primary menu through which you can access the administrative screens.
Using the Administration System

In order to use the Administration System, both CICS and Connect:Direct must be installed and working on your mainframe. You must also be using an IBM 3270 terminal or equivalent. Display the Connect:Direct Administration Primary Menu by using the CDA transaction.
Using the Primary Menu

The Connect:Direct ADMINISTRATION PRIMARY MENU is the root of the administration menu hierarchy and is the access key to all the other features of the Connect:Direct Administration System. Following is an example of the Primary Menu.
Connect:Direct ADMINISTRATION PRIMARY MENU OPTION ==> _ 10:17:29
C I N S U
... ... ... ... ...
CONFIGURATION INTERFACE STATUS NODE STATUS SIGNON DEFAULTS USER STATUS To restrict U :
CICS USERID ==> _____________ CICS TERMID ==> _____ Connect:Direct NODE ==> _________________________ PF keys: 3 Exit
2-2
Connect:Direct OS/390 CICS Users Guide
Entry Fields
The following table describes each option.
Option C Description Selecting this option takes you to the CONFIGURATION menu. If you need to maintain CICS Interface configuration information, select this option. Selecting this option takes you to the INTERFACE STATUS menu. If you need to activate or deactivate the Connect:Direct interface, select this option. Selecting this option takes you to the NODE STATUS menu. If you need to view the status of nodes that users of the CICS Interface can sign on to, and information about the sessions and tasks under the node, select this option. Selecting this option takes you to the SIGNON DEFAULTS menu. If you need to maintain user signon default information, select this option. Selecting this option takes you to the USER STATUS menu. If the you need to check on a particular userid and the Connect:Direct activities associated with that userid, or if you need to cancel a user task or signon, select this option.
The following fields are not required under option U, but you can use them to limit the scope of the display:
Field CICS USERID CICS TERMID Connect:Direct NODE Description This 8-character field contains the Connect:Direct CICS signon ID. This 4-character field contains a valid terminal ID. This 16-character field contains a valid Connect:Direct node name.
Chapter 3
Maintaining Configuration Information
The CICS Interface provides a variety of configuration options to allow you to define the resources that can be accessed, limit the scope of functions provided to users, and optimize the performance of the system. All CICS Interface configuration information is contained in a single file (CONFIG), which is defined and initially loaded at product installation.
Configuration Categories
The configuration parameters divided into the following categories:
! ! !
Control Record DTF Node Records Network Node Records
Control Record
The Connect:Direct OS/390 Control Record contains information defining the operational characteristics of the Connect:Direct OS/390 system. This information includes flags that activate or deactivate system-wide features of the CICS Interface and parameters that govern the performance of the system. The Control Record is initially loaded during the installation process. The CICS Interface online administration facilities allow you to modify the contents of this record only. Any modifications performed while the CICS Interface is active are immediately reflected in the execution environment.
DTF Node Records

A CICS Interface user has the ability to access multiple Connect:Direct DTFs for the purpose of copying files from that node to other nodes, submitting Processes, and gathering and reporting on statistical information. The DTF Node Records contain information identifying any node eligible to be signed on to by the CICS Interface and defining the rules governing access to that node (such as ESF access, output limits, and so forth). Note: One DTF Node Record is required for each Connect:Direct DTF to which the CICS Interface can sign on directly. The first of these records is defined and loaded at product installation.
3-2
Understanding Subtasks
Connect:Direct DTF node information describes each DTF node available to the CICS Interface. At the startup of the Interface, a subtask called CST (controller subtask) is attached by CICS. The CST in turn attaches other subtasks, called WSTs (worker subtasks). WSTs establish and manage a VTAM session with a DTF, passing Connect:Direct commands, and receiving returned information. One WST communicates with only one DTF, but multiple WSTs can communicate with one DTF.
Network Node Records

To facilitate the task of copying files from one node to another, the CICS Interface provides a means of predefining frequently used nodes, relieving you of the need to know specific information about nodes to be accessed. Nodes defined in Network Node Records display as a numbered list in the COPY FILE BETWEEN NODES screen. You can select nodes by number and provide only that information relating to the file to be sent or received.
Accessing the Administration Configuration Screen

To access the Connect:Direct ADMINISTRATION CONFIGURATION screen, select option C from the PRIMARY MENU. The CONFIGURATION screen enables you to display and maintain the Control Record, DTF Node Records, and the Network Node Records. Following is an example of the screen.
Connect:Direct ADMINISTRATION CONFIGURATION OPTION ==> _ 10:25:28
C ... CONTROL RECORD D ... DTF NODE RECORDS N ... NETWORK NODE RECORDS
PF keys:
3 Exit
Entry Fields
The following table describes each configuration option.
Option C Description Selecting this option, and pressing Enter takes you to the CONTROL RECORD screen. If you need to update the CONTROL RECORD with information affecting the operating characteristics of the CICS Interface, select this option.
Chapter 3 / Maintaining Configuration Information
3-3
Option D
Description Selecting this option, and pressing Enter takes you to the DTF NODE RECORDS screen. If you need to view the characteristics of a DTF NODE, such as node name, number of worker subtasks, and entries in the work queue, select this option. Selecting this option, and pressing Enter takes you to the NETWORK NODE RECORDS screen. If you need to view the characteristics of a NETWORK NODE, such as node name, node description, and node type, select this option.
Updating the Control Record

To access the Connect:Direct ADMINISTRATION CONTROL RECORD UPDATE screen select option C from the CONFIGURATION screen, and press Enter. Only one CONTROL RECORD exists for the CICS Interface system. This control record contains global configuration parameters. Following is an example of the screen.
Connect:Direct ADMINISTRATION CONTROL RECORD UPDATE AUTO.SIGNON ............................ SIGNON.REENTRY ......................... Connect:Direct.EQ.CICSID ............... SKIP.SIGNON.PANEL ...................... CICS.TRANSACTION.CODE (MONITOR) ........ CICS.TRANSACTION.CODE (STARTUP) ........ CICS.TRANSACTION.CODE (PRINT) .......... CICS.TRANSACTION.CODE (ESS) ............ CST.RETRY.INTERVAL ..................... SESSION.RETRY.INTERVAL ................. ESF.RETRY.INTERVAL ..................... WORK.RETRY.INTERVAL .................... MONITOR.INTERVAL ....................... INACTIVE.INTERVAL ...................... MAX.SIGNON ............................. MAX.TASKS .............................. STORAGE.SUBPOOL ........................ MENU OPTIONS: CF Y SB Y SS Y PF keys: 3 Exit Y N Y N CDM CDI CDP CDE 000500 0100 001500 0015 30 003000 0100 02 127 Y Y Y Y 16:13:15
OR OR OR OR
N N N N
HHMMSS MMSS HHMMSS MMSS SS HHMMSS 01-99 002-127
SP Y
SD Y
SN Y
MD Y
Y OR N Clear Reset
9 Update
Enter Edit
3-4
Entry Fields
The entry fields are:
Field AUTO.SIGNON Description Specifies whether Connect:Direct OS/390 automatically signs you on if a signon defaults record is defined with a CICS userid matching the userid that you specify at CICS signon. The signon defaults record for that CICS user must specify a valid Connect:Direct userid, password and DTF node name. If you specify Y, auto-signon is used if the required information is available; if you specify N, auto-signon is not used. The default is Y. Specifies whether the CICS Interface remembers that a CICS user previously signed on to the IUI. If this feature is enabled, the user is able to exit the CICS Interface to perform another CICS function and reenter without signing on again. Signon reentry is not performed for a user who signs off CICS and signs back on again between CICS sessions signon reentry is only in effect after the first signon to the CICS Interface. If you specify Y, signon reentry is performed when appropriate; if you specify N, signon reentry is not performed. The default is N. Specifies whether the CICS Interface denies a signon attempt if the Connect:Direct userid does not match the CICS userid specified at CICS signon. If you specify Y, a signon is rejected if the IDs do not match; if you specify N, no check takes place. The default is Y. Specifies an optional CICS signon interface that does not require you to retype a userid and password. Validity of this approach depends upon a secure environment existing prior to you selecting the CICS Interface; in other words, userid and password validation by a security subsystem (CA-ACF2, RACF, and so forth) upon original signon to the system. Enable this option by typing Y for this parameter on the Control Record Update screen. The control record can also be set during installation by typing SKIP.SIGNON.PANEL=Y on the CONFIGURATION FILE - CONTROL PARAMETER RECORD screen. The default is N. Specifies the 1-4 character transaction codes to be used for the CICS Interface monitor transaction. The monitor transaction scans for pending requests from users and for completed work by Connect:Direct. If the MONITOR TRANSACTION CODE is not specified during installation, it defaults to CDM. If you change this parameter, you must also change the supplied transaction definition. Specifies the 1-4 character transaction codes to be used for the CICS Interface start transaction. If you use the startup PLT to activate the CICS Interface at CICS initialization, this transaction is submitted to run immediately following the completion of CICS initialization processing. If you do not specify the STARTUP TRANSACTION CODE parameter during installation, it defaults to CDI. If you change this parameter, you must also change the supplied transaction definition. Specifies the 1-4 character transaction codes to be used for the CICS Interface print transaction. This transaction is attached to the CICS printer in response to CICS print requests. If the PRINTER TRANSACTION CODE parameter is not specified during installation, it defaults to CDP. If you change this parameter, you must also change the supplied transaction definition. Print requests are handled by writing print lines to the CICS Transient Data Area (TDA). When the data is ready for output, a transaction sends the data to the CICS printer specified in the SIGNON DEFAULTS. Specifies the 1-4 character transaction code to be used for the Connect:Direct OS/390 Event Services Support. If this parameter is not specified during installation, it defaults to CDE. If you change this parameter, you must also change the supplied transaction definition.
SIGNON.REENTRY
Connect:Direct.EQ.CICSID
SKIP.SIGNON.PANEL
CICS.TRANSACTION.CODE (MONITOR)
CICS.TRANSACTION.CODE (STARTUP)
CICS.TRANSACTION.CODE (PRINT)
CICS.TRANSACTION.CODE (ESS)
3-5
Field CST.RETRY.INTERVAL
Description Specifies the time interval (in hours, minutes and seconds) between attempts to restart an abended CST (controller subtask). The controller subtask is an operating system subtask responsible for monitoring the worker subtasks responsible for interaction with active Connect:Direct DTFs defined in DTF Node Records (that is, DTFs to which CICS users can sign on). The default is 000500 (5 minutes). Specifies the time interval (in minutes and seconds) between attempts to establish a VTAM session with a DTF defined in a DTF Node Record (that is, a DTF to which CICS users can sign on directly). The default is 100 (1 minute). Defines the time interval (in hours, minutes and seconds) between attempts to establish a primary session with a Connect:Direct DTF when, during a prior attempt, the DTF is not active and the node is activated in ESF mode. A node is activated in ESF mode only if the DTF it defines supports ESF. The default is 001500 (15 minutes). Specifies the time interval (in minutes and seconds) between the time a unit of work is submitted but cannot be placed in the work queue for a particular node and the time that unit of work is cancelled. The size of the work queue for a particular node is governed by the ENTRIES IN WORK QUEUE parameter in the DTF Node Record. The default is 0015 (15 seconds). Contains the time interval, expressed as seconds, between scans for work by the monitor transaction. This parameter is a 2-character field. The monitor watches all Processes, queues, tasks, and task lengths, and regulates the flow of tasks in the system to ensure that any particular task does not seize the computer resources. When all Processes and tasks are completed or pending action by the DTF, the monitor waits for the specified interval before rescanning the work queue. The default is 30 (seconds). Specifies the amount of time (in hours, minutes and seconds) that a worker subtask (WST) is allowed to be inactive before it is detached by the controller subtask (CST). The default is 003000 (30 minutes). Contains the maximum number of CICS users and reflects the relative size of the signon table file. This parameter is a 4-character field. The default is 100 entries. Contains the maximum number of simultaneous subtasks that can be attached in the CICS address space. This parameter is a 2-character field. Specify this field as the total of the worker subtask counts for all DTF Node Records defined to the CICS Interface. The default is 2. Contains the number of the operating system storage subpool from which the CICS Interface acquires operating system storage. This parameter is a 3-character field. Numbers 002-127 are user-defined (numbers 000, 001, 128-255 are system-defined) areas of storage related to each other usually by the requirements of your session. DTF keeps track of all storage for a given user Process and task. The default is subpool 127.
SESSION.RETRY.INTERVAL
ESF.RETRY.INTERVAL
WORK.RETRY.INTERVAL
MONITOR.INTERVAL
INACTIVE.INTERVAL
MAX.SIGNON
MAX.TASKS
STORAGE.SUBPOOL
Menu Options
The following options contain a Y or N which enables or disables the options on the PRIMARY MENU of the general user. You can use these Y/N flags to determine the level of functionality to be provided by Connect:Direct OS/390. These options affect all users of Connect:Direct OS/390. If you want to limit the functionality available to specific users, you must use either the authorization functions of Connect:Direct (select only the appropriate
3-6
options when defining that user in the Connect:Direct Authorization File) or the Connect:Direct Security exit (set an Authorization Bit Mask to allow or restrict the appropriate options).
Option CF Description Contains the toggle to turn off the COPY FILE option on the PRIMARY MENU. The field is one character long; Y permits you to copy files; N denies permission. Contains the toggle to turn off the SUBMIT PROCESS option on the PRIMARY MENU. The field is one character long; Y permits you to submit Processes; N denies permission. Contains the toggle to turn off the SELECT STATISTICS option on the PRIMARY MENU. The field is one character long; Y permits you to select statistics; N denies permission. Contains the toggle to turn off the SELECT PROCESS option on the PRIMARY MENU. The field is one character long; Y permits you to select Processes; N denies permission. Contains the toggle to turn off the SIGNON DEFAULTS option on the PRIMARY MENU. The field is one character long with a Y or N; Y grants permission to change default signon options; N denies permission. Contains the toggle to turn off the CHANGE SIGNON option on the PRIMARY MENU. The field is one character long with a Y or N; Y grants permission; N does not. Contains the toggle to turn off the MESSAGE DISPLAY option on the PRIMARY MENU. The field is one character long with a Y or N; Y grants permission to use this option; N does not.
SB
SS
SP
SD
SN
MD
Updating DTF Node Records

The Connect:Direct ADMINISTRATION DTF NODE RECORDS screen is accessed by selecting option C on the PRIMARY MENU, then by selecting option D on the CONFIGURATION screen, and pressing Enter. One DTF node record exists for each DTF node which Connect:Direct OS/390 users can sign on to directly. Following is an example of the screen. Note: Changes made to the DTF node record parameters are immediately reflected in the active system.
Connect:Direct ADMINISTRATION DTF NODE RECORDS DTF NODE NAME NETMAP DDNAME DUMMY ID FOR DTF SIGNON SUPPRESS CONNECTION AT STARTUP ESF SIGNON ALLOWED MAXIMUM WORKER SUBTASKS ENTRIES IN WORK QUEUE OUTPUT RECORD LIMIT SLOW RESPONSE NOTIFICATION ________________ ________ ________ _ _ __ ___ _____ ____ 16:17:53
Y OR N Y OR N
MMSS
PF keys:
3 Exit 5 Add Enter Read/Edit
6 Delete 7 Prev Clear Reset
8 Next
9 Update
3-7
Entry Fields
The following table describes the Entry fields:
Field DTF NODE NAME NETMAP DDNAME Description Contains the name of a DTF node. This is a 16-character field. Specifies the DDNAME of the Connect:Direct network map file to be used when initiating a signon to this node. The network map must have an adjacent node definition for this node, but need not be exactly the same network map file the node is using. You must code this value; no default is available. Note: The NETMAP DDNAME is in the File Control Table and in the CICS startup JCL. Alternately, If you are using the CSD file for Connect:Direct file definitions, you must enable the NETMAP DDNAME as an FCT entry in a CEDA group initialized during CICS startup (in this case, you do not need the DDNAME in the CICS startup JCL). You must have one network map file for each node and you must have the DTF node record for each node you want to sign on to. Specifies the Connect:Direct userid to be used to initially establish the VTAM session with the DTF. Multiple CICS userids are required if a DTF can have multiple CICS Interface systems signed on concurrently. If you are using the DMGSECUR macro to define your Connect:Direct security exit, this parameter must match the CICS parameter coded for that macro. You must code this value; no default is available. Contains the toggle for startup connections. This is a 1-character field. If the field contains Y, the connection between the specified DTF node and the Connect:Direct OS/390 system is suppressed when the Connect:Direct OS/390 software is started. If the field contains N, then the connection is made. The default is Y. Specifies whether the Extended Submit Facility is to be supported for this node by Connect:Direct OS/390. The DTF identified in this record must support ESF in order to sign on in ESF mode using Connect:Direct OS/390. The default is N. Specifies the maximum number of WSTs (worker subtasks) to be used for this node. Define one WST per parallel session defined for this node. Do not exceed the MAX TASKS value in the Control Record with the total number of worker subtasks defined for all DTF NODE records in the system. The default is 2. Specifies the maximum number of actual requests to be allowed on the pending work queue for this node. An excessive value here could result in an inordinate response time for terminal users. During installation, the default is the MAXIMUM WORKER SUBTASKS specification. Specifies the upper limit on the number of lines of output that are accepted in response to a SELECT PROCESS or SELECT STATISTICS command. Output from these commands is stored in CICS temporary storage until viewed or explicitly deleted. The default is a limit of 800 80-byte records. Contains the time interval, expressed as minutes and seconds, after which Connect:Direct OS/390 notifies you of potential problems with slow response. This is a 4-character field. The default is 0200 (2 minutes).
DUMMY ID FOR DTF SIGNON
SUPPRESS CONNECTION AT STARTUP
ESF SIGNON ALLOWED
MAXIMUM WORKER SUBTASKS
ENTRIES IN WORK QUEUE
OUTPUT RECORD LIMIT
SLOW RESPONSE NOTIFICATION
Updating Network Node Records

To access the Connect:Direct ADMINISTRATION NETWORK NODE RECORDS screen, select option C from the PRIMARY MENU, select option N from the CONFIGURATION screen, and press Enter. The screen
3-8
fields are scrollable, and allow you to view the contents of the network node records. Following is an example of the screen.
Connect:Direct ADMINISTRATION NETWORK NODE RECORDS NETWORK NODE NAME NETWORK NODE DESCRIPTION NODE TYPE __ ________________ ______________________________ 1=OS/390 2=VM 5=TANDEM 6=WIN95 9=UNIX 10=NETWARE 13=MVS 3=VSE 7=OS/2 11=WINDOWS 4=VMS 8=OS/400 12=MSP 14:44:36
PF keys:
8 Next
9 Update
Because you can type the node name and environment on the COPY FILE BETWEEN NODES screen, it is not required that you define every node participating in a COPYFILE on the NETWORK NODE RECORDS screen. Note: Changes made to the Network Node Record parameters are immediately reflected in the active system.
Entry Fields
The following table describes the entry fields.
Field NETWORK NODE NAME NETWORK NODE DESCRIPTION NODE TYPE Description (16-character field) contains the name of the node.
(30-character field) contains a description of the node.
(1-character field) contains the environment number. Valid environment numbers are as follows: 1 for OS/390 2 for VM 3 for VSE 4 for VMS 5 for TANDEM 6 for WIN95 8 for OS/400 9 for UNIX 11 for WINDOWS
Chapter 4
Working with the Administration Interface
This chapter describes how to work with the Connect:Direct Administration Interface.
Using the Connect:Direct Administration Interface Screen

To access the Connect:Direct ADMINISTRATION INTERFACE screen, select option I from the PRIMARY MENU and press Enter.
Connect:Direct ADMINISTRATION INTERFACE OPTION ==> 10:30:37 Connect:Direct VER VV REL RR MOD MM
A M I S
... ... ... ...
ACTIVATE INTERFACE START MONITOR SHUTDOWN INTERFACE (IMMEDIATE) SHUTDOWN INTERFACE (NORMAL)
INTERFACE STATUS PENDING REQUEST MONITOR TASK NUMBER ACTIVE TASKS
ACTIVE NONE 25 0
PF keys:
3 Exit
ENTER Refresh/Process
The INTERFACE screen is the key to activating, monitoring, and shutting down the CICS Interface between CICS and the active Connect:Direct DTF nodes. From the INTERFACE screen, you can manually initialize and terminate the operating system subtasks that perform the interaction with Connect:Direct.
4-2
Entry Fields
The following table describes each option for the INTERFACE screen.
Options A Description Selecting this option, and pressing Enter activates the interface and automatically starts the monitor transaction. Selecting this option, and pressing Enter starts the monitor transaction. Only use this option in the event of a monitor transaction abend. Selecting this option, and pressing Enter performs an immediate (hard) shutdown of the interface. All Connect:Direct user sessions are terminated, regardless of status. Selecting this option, and pressing Enter, performs a normal (soft) shutdown of the interface. All Connect:Direct user sessions are allowed to complete execution.
System Fields
The following table describes the System fields:
Field VER REL MOD INTERFACE STATUS Description (2-character field) contains the version number of the CICS Interface software. (2-character field) contains the release number of the CICS Interface software. (2-character field) contains the modification number of the CICS Interface software. (21-character field) contains ACTIVE or INACTIVE, depending upon the state of the interface. The field contains ACTIVE if the interface is active and changes to INACTIVE if the interface is deactivated. (18-character field) contains either NONE, if no activate or shutdown request is pending, or the type of request being processed. (11-character field) contains the number of the monitor transaction or a message such as NOT RUNNING, if the interface is not active. (2-character field) contains the number of the active tasks.
PENDING REQUEST MONITOR TASK NUMBER ACTIVE TASKS
Operating the CICS Interface

In order for the CICS user interface to perform its function, a connection must exist between it and a Connect:Direct DTF. This facility can be local (within the same VTAM domain) or remote (residing in another domain). This connection is accomplished using operating system subtasks that are attached in the CICS address space at the CICS Interface startup. The subtasks perform two types of functions:
!
One or more Worker Subtasks (WSTs) are attached for each active link to a Connect:Direct DTF. These subtasks are responsible for establishing a link to the DTF, passing commands to it, and receiving any results.
Chapter 4 / Working with the Administration Interface
4-3
A single Controller Subtask (CST) is created to monitor the work of all WSTs in the system and perform communications functions with the user interface portion of CICS. Acquires CICS Interface work areas, such as the signon table, the work queue areas, and so forth Enables a task control global exit point and its associated global work area Reads the configuration information from the configuration file and places that information in the global work area Attaches the CST subtask Checks for any DTF nodes that are to be activated at initialization and passes information to the CST task to allow it to create the appropriate WSTs and establish the link with the DTF
Initialization of the CICS Interface invokes programs that perform the following functions:
! ! ! ! !
Note: The CICS Interface module is also available for the interface autostart at CICS startup. When the module is in the PLTPI, you can start CICS without starting the interface by including a special DD card in the CICS startup JCL deck: //NDMINIT DD DUMMY. If present, NDMINIT will not start the interface as part of CICS initialization. The interface can then be started manually.
Monitor Transaction
In addition to these operating system subtasks, a CICS monitor transaction is created to accept input from the user interface, pass it to the CST, and route the output to the appropriate user. This transaction is also responsible for detecting a loss of the CST subtask due to an error condition and performing a restart. The monitor transaction is activated at the CICS Interface startup and remains in the system for the life of the online region. Monitor activities include the following:
! ! ! ! ! ! !
Restarting the interface in case of an abend Watching for DTF requests which are taking too long Forcing retry of requests still in the queue Forcing retry of DTF node session establishment Attempting to switch from ESF to primary (DTF connected) mode Clearing non-terminal signon table entries, at end of transaction Clearing signon table entries in case of abends
Interface Tasks
Although CICS runs a number of subtasks (such as journaling and VSAM handling), CICS can be regarded as a single task. All CICS transactions that can generate Connect:Direct requests run from this single CICS task. The CICS Interface runs as a set of separate tasks in the CICS address space. At the startup of the CICS Interface, a subtask called CST (controller subtask) is attached by CICS.
Interface Startup
This isolates CICS from all the non-CICS work involved in communicating to the Connect:Direct DTF through the Connect:Direct API. A CICS Interface monitor transaction is also invoked as part of interface startup to support and monitor interface operation. The CST in turn attaches other subtasks, called WSTs (worker subtasks), organized by node. The WSTs establish and manage the DTF sessions, passing Connect:Direct commands, and receiving returned information. The CST controls traffic between all CICS Interface transactions and each WST.
4-4
Interface Subtask Management

Each WST handles requests for CICS users through the CST. One WST communicates with only one DTF, but multiple WSTs can communicate with one DTF. The DTF-connected WSTs are not associated with any particular CICS transactions. The various Connect:Direct requests generated by CICS Interface users are handled by any of the multiple WSTs which are for a particular DTF node. The CST oversees all the WSTs, and is responsible for coordinating work generated by CICS transactions. One WST is attached per node at the CICS Interface startup, as defined in the CONFIGURATION file. Additional WSTs for a node are attached as needed, based on concurrent CICS Interface user demand. The maximum number of WSTs (tasks) attached globally for the interface and per DTF node is defined with CONFIGURATION control and DTF node parameters. The DTF node connection limit is edited to be no larger than the number of CICS interactive applications specified in the Network Map for that node. When an attached WST becomes inactive (is not used for any requests) for a period of time, it is detached by CST. The inactive interval is defined with a CONFIGURATION control option. You can suppress WST activation by DTF node with a CONFIGURATION DTF node parameter.
Interface Request Management

CICS user requests are placed on a work queue with one queue per node. The one or more WSTs attached per node dispatch work from the queue. Maximum queue length by node is defined with a CONFIGURATION DTF node parameter which defines the number of queue entries. When WST (session limit) is reached and additional WSTs cannot be attached to dispatch work from the queue, requests remain on the work queue until a WST becomes available. When the number of allowed WSTs for a given node is held to a minimum, yet user activity for the given node is high, increase the number of queue entries. Work queue size is also affected by the CONFIGURATION control option worker retry interval which defines the time elapsed between attempts to obtain a free WST to dispatch work present on the work queue. Connect:Direct user requests are rejected with a DTF busy message, when a DTF node queue reaches its maximum allowed number of entries. The CONFIGURATION DTF node parameter defines worry time. A message is written to the log when a request to that node takes longer than the specified amount of time. No action is taken by the CICS Interface to automatically abort any requests which take too long. The CICS Interface also has one system queue for system commands, such as SHUTDOWN, QUIESCE, to dispatch system requests. You cannot adjust the system queue size.
Interface VTAM Session

In cases where a WST/DTF VTAM session is active, but becomes inactive, the CICS Interface quiesces the node. Pending requests are allowed to complete, even though they can fail. The number of WSTs for the node is reduced to one. At this point, if the WST is in session with a local DTF, and ESF mode is allowed, the WST switches to ESF mode. An ESF MODE message is displayed to IUI users, stating that a Connect:Direct session error occurred, but ESF MODE is available. Under ESF operation, only the SUBMIT options are displayed on the PRIMARY MENU.
Chapter 4 / Working with the Administration Interface
4-5
ESF mode operation is enabled for the entire interface through a CONFIGURATION control parameter; ESF mode operation is enabled for each user through a user profile parameter. When a WST fails to establish or drops a DTF session, and ESF is not allowed, then the WST remains attached, but all user requests for the node are rejected. The WST periodically tries to establish or re-establish (retry) a session with the associated DTF. The CONFIGURATION control parameter session retry interval defines the time lapsed between retries for session connection. An additional CONFIGURATION control parameter, the ESF session retry interval, defines the time elapsed between retries of a dummy DTF session to check if ESF mode has returned to primary mode.
4-6
Chapter 5
Viewing Node Status
This chapter describes how to view the status of nodes that are part of your Connect:Direct network.
Accessing the Node Status Screen

To access the Connect:Direct ADMINISTRATION NODE STATUS screen, select option N from the PRIMARY MENU and press Enter. The Node Status screen enables you to check the status of all DTF nodes eligible for access by the CICS Interface, and you can selectively activate, deactivate, and view pending work for all DTF nodes. Following is an example of the Node Status screen.
Connect:Direct ADMINISTRATION NODE STATUS CICS STATUS -----INACT ACTIVE ADMIN REQUEST ------SESS TYPE ---NONE PRIM SESSION DATE/TIME OR SESSION MSGID ----------------06/19/1998 09:57:18 MAX TASKS ----3 2 10:30:37
DTF NODE NAME ------------_ NODE1 _ NODE2
CURR TASKS ----0 1
CURR WORK ---0 0
Line commands:
A W
Activate (start first task) Work queue display ENTER Refresh/Line cmd
I S
Shut immediate Shut normal
PF keys:
3 Exit
Press PF7 and PF8 to scroll backward and forward, respectively, through the list of DTF nodes connected to the Connect:Direct OS/390 session.
Line Commands
The CICS user interface provides the ability to log on to any Connect:Direct DTF in your network and perform Connect:Direct operations using that node as your Process primary node. DTFs to be accessed must be identified in DTF Node Records in the configuration file along with the configuration parameters to be used when communicating with that node.
5-2
Line commands are as follows:

Line command A W Description Type this option in the field to the left of the DTF node name and press Enter to activate the node. Type this option and press Enter, to access the WORK QUEUE screen, if work for this node is being processed. See page 5-3 for how to use the WORK QUEUE screen. Type this option and press Enter to perform an immediate (hard) shutdown of the node. All Processes for this node are forced to stop, regardless of status. Type this option and press Enter to perform a normal (soft) shutdown of the node. All Processes for this node are allowed to complete execution.
System Fields
The system fields follow:
Field DTF NODE NAME CICS STATUS Description (16-character field) contains the DTF node name as typed in the DTF Node Record. (6-character field) contains the status of the node, such as ACTIVE and INACT. ACTIVE - The node is activated, either by the CICS Interface initialization or manually. INACT - The node is not active. This 8-character field contains the type of administrative request affecting the status of the node, such as ACTIVATE, SHUTIMM, or SHUTNORM. ACTIVATE - The node is activated. SHUTNORM - A normal shutdown of the node is requested, and the node is quiescing. SHUTIMM - An immediate shutdown of the node is requested, and the link with that DTF is being terminated. This 4-character field contains the type of session held with this DTF node, as follows: NONE - No session currently exists with this DTF node. PRIM - The CICS Interface is currently in session with the DTF node. ESF - The DTF is not active, but supports the Extended Submit Facility. The CICS Interface is accepting requests allowed in ESF mode. This 17-character field contains either the date and time that the connection to this DTF is activated, or the MSGID of the last message issued for this DTF node during activation or deactivation. This 5-character field contains the maximum number of subtasks that are attached to Process requests directed at this node. This 5-character field contains the current number of subtasks attached to Process requests directed at this node. This 5-character field contains the number of subtasks currently processing requests directed at this node.
ADMIN REQUEST
SESS TYPE
SESSION DATE/TIME
MAX TASKS
CURR TASKS
CURR WORK
Chapter 5 / Viewing Node Status
5-3
Viewing the Work Queue

The Connect:Direct Work Queue is defined for each node to dispatch Connect:Direct requests and responses. The DTF node configuration file contains information required by the CICS Interface to manage the DTF VTAM or ESF sessions. Each WST uses the standard Connect:Direct API to manage the DTF or ESF session. To access the Connect:Direct ADMINISTRATION WORK QUEUE screen, select option W from the NODE STATUS screen and press Enter. The WORK QUEUE screen fields contain the data describing the tasks in the work queue for each CICS user on a Connect:Direct DTF node. Following is an example of the screen.
Connect:Direct ADMINISTRATION WORK QUEUE - NODE "nodename" CICS TERM ---M064 LAST TASK# ----00271 CURR CMD --SB REQUEST DATE/TIME ----------------06/21/1998 11:47:13 10:30:37 Page 01 of 01 WORK TASK ---0346
CICS ID ------ID1
USERID -------ID1
TD CTR -----00282
PF keys:
3 Exit
7 Bwd
8 Fwd
12 Node USER STATUS
ENTER Refresh
Scroll backward using PF7 and forward using PF8 to view the entries. Press PF12 to view to the USER STATUS screen, and then press PF3 to get back to the WORK QUEUE screen.
System Fields
System fields are as follows:
Field NODE Page XX of YY CICS ID USERID CICS TERM LAST TASK# CURR CMD Description (16-character field) contains the node name associated with the work queue data. (13-character field) contains the number of the current page for the work queue list. (8-character field) contains the CICS userid of the user submitting the work. (8-character field) contains the CICS userid of the user submitting the work. (4-character field) contains the terminal ID from which the work is submitted. (5-character field) contains the transaction number of the task submitting this request. (2-character field) contains the representation of the current command executed by the task (for example, CF, SB, SS). (17-character field) contains the date and time the work is submitted.
REQUEST DATE/TIME TD CTR
(5-character field) contains the number of bytes (counted by the transient data counter) indicating how much data is written by the exit module for a transaction.
5-4
Field WORK TASK
Description (4-character field) contains the number of the work task.
Chapter 6
Maintaining Signon Defaults
Connect:Direct enables you to set default CICS signon information. This information is not required but it can make Connect:Direct easier to use. This chapter describes signon defaults.
How Connect:Direct Uses Signon Defaults

When a user enters a Connect:Direct OS/390 CICS transaction, Connect:Direct uses the CICS userid to read profile data set. If it finds a profile record, Connect:Direct uses the records information to control what the user can do. If the users signon defaults record includes a userid and password, Connect:Direct automatically signs on the user. If the signon defaults record do not include a userid and password, Connect:Direct prompts the user for a userid and password before allowing access. After accessing Connect:Direct, you can change your own signon defaults using the SD function.
6-2
Accessing the Signon Defaults Screen

To access the Connect:Direct Administration Signon Defaults screen select option S from the Primary Menu and press Enter. The screen is shown in the following figure.
Connect:Direct ADMINISTRATION SIGNON DEFAULTS CICS USERID ==> ________ 14:59:46
**Connect:Direct** USERID ==> ________________________________________________________________ PASSWORD==> DEFAULT NODE ESF MODE ALLOWED UPPER CASE PRINT CICS PRINTER PNODE ACCT DATA SNODE ACCT DATA ==> ==> ==> ==> ==> ==> ________________ _ Y OR N _ Y OR N ____ _______________________________________________ _______________________________________________ NO_
Do you want all commands for this session to be CASE sensitive? ==>
PF keys:
8 Next
9 Update
Entry Fields
The following table describes the entry fields.
Field CICS USERID USERID PASSWORD DEFAULT NODE Description (8-character field) is the acceptable userid for the CICS signon. (64-character field) is the acceptable userid for the Connect:Direct signon. (64-character field) is the valid password associated with the Connect:Direct userid. (16-character field) is the name of the default Connect:Direct node. The user is automatically signed on to this node if it is active, or is denied access if it is not active. (1-character field) is the permission for use of the ESF. If the field contains Y, permission is allowed. If the field contains N, permission is denied. (1-character field) is the switch for upper case printing. If the field contains Y, all printed output is upper case. If the field contains N, the printed output is upper and lower case. (4-character field) is the designation for the CICS printer used for print requests from this user. (50-character field) is the primary node accounting data for allocation of budget to CPU time, I/O, and other computer resources. (50-character field) is the secondary node accounting data for allocation of budget to users for CPU, I/O, and computer resource time.
ESF MODE ALLOWED UPPER CASE PRINT CICS PRINTER PNODE ACCT DATA SNODE ACCT DATA
Chapter 6 / Maintaining Signon Defaults
6-3
System Fields
The following table describes the system field.
Field PASSWORD MESSAGE Description (44-character field) indicates whether the users signon defaults record has a password. This field is displayed to the right of the PASSWORD field.
6-4
Chapter 7
Viewing User Status
Periodically view the status of a user to determine:

! ! !
User access to a resource Actions users are performing while using a resource Resolve problems encountered by users
Connect:Direct provides the user status function for you to view information about users of the system and, if necessary, intervene to resolve error situations. You can either view all users of the system, a single user (optionally qualified by CICS userid or terminal ID) or a group of users (optionally qualified by Connect:Direct DTF node).
Accessing the User Status Screen

To access the Connect:Direct ADMINISTRATION USER STATUS screen from the PRIMARY MENU, select option U and press Enter. You have the option, while on the PRIMARY MENU screen, to restrict the scope of the status display. Restrict the scope by specifying the CICS userid, terminal ID and Connect:Direct node that you want to display on the USER STATUS screen. To see all signed-on users, do not restrict your selection. Following is an example of the USER STATUS screen.
Connect:Direct ADMINISTRATION USER STATUS CICS TERM ---M064 SESS TYPE ---PRIM LAST TASK # -----45 10:30:37
CICS ID ------_ MASTER
USERID -----ID1
DTF NODE NAME ------------"dtfnodename"
STATUS -----CICS
MSGID ----SAFA000I
Line commands:
Free user
C T
Free user and cancel users subtask Free user and terminate users signon ENTER Refresh/Process
PF keys:
3 Exit
10 Left
11 Right
7-2
Options
You normally select the following options in the underscore field to the left of the CICS userid, when a user security violation or resource allocation is abused:
Option F C Description Selecting this option frees any user from use of the CICS Interface system. Selecting this option frees any user from use of the CICS Interface system, and cancels that users subtask. Selecting this option frees any user from use of the CICS Interface system, and terminates that users signon.
System Fields
The following table describes the systems fields:
Field CICS ID CICS TERM SESS TYPE USERID DTF NODE NAME STATUS LAST TASK # MSGID Description (8-character field) contains the CICS userid of all currently signed-on users. (4-character field) contains the CICS terminal ID of all currently signed-on users. (4-character field) contains the session type (PRIM or NONE). (8-character field) contains the Connect:Direct userid of all currently signed-on users. (16-character field) contains the DTF node name the user is signed on to. (7-character field) contains the STATUS of a user. contains the last task number of a user Process. contains the message ID of the last message for a given user.
If you press PF11 to scroll right on the screen, the following fields are displayed:
Field TD CTR Description (5-character field) contains the number of bytes (counted by the transient data counter) indicating how much data is written by the exit module for a transaction. contains the time of the last signon. contains the time of the last request.
LAST SIGNON LAST REQUEST
Chapter 8
Operational Considerations
This chapter describes the following CICS operational considerations:

! ! ! ! ! ! ! !
Signing on to multiple Connect:Direct DTFs from a single CICS Interface IUI Signing on to a single DTF from multiple CICS Interface IUI facilities Performing an immediate or uncontrolled shutdown Restarting Task abends Accessing accounting and logging information Using the Extended Submit Facility (ESF) Specifying Connect:Direct signon parameters Understanding CICS Interface data sets
Signing On to Multiple DTFs from a Single IUI

You can use the Connect:Direct OS/390 IUI to sign on to multiple Connect:Direct DTFs on either local or remote processors. To take advantage of this facility, you must consider the following:
!
You must provide VTAM access to the DTF you want to sign on to. For local DTFs (within the control of the same VTAM subsystem), you must provide IUI APPLIDs for use by both the ISPF and CICS IUI facilities. If the DTF facilities are located on remote processors, you must define the IUI APPLIDs for those DTFs to the local VTAM subsystem as cross-domain resources. For each DTF you want to access through the CICS IUI, you must define a DTF Node Record for that facility in your CICS configuration file. You can define the DTF Node Record by using the configuration update facilities of the CDA transaction. The DTF node record in your configuration file must include the DD name of a Network Map file in order to communicate with the remote Connect:Direct DTF. This Network map must have the remote DTF defined as an adjacent node. The Connect:Direct Network Map enables segregation of API VTAM APPLIDs such that the CICS Interface can have a pool of APPLIDs, DMBATCH can have a pool, and ISPF IUI can have yet another pool. The adjacent node statement in the Network Map source provides for the segregation of VTAM APPLIDs between the various types of Connect:Direct API connections. The format is as follows.
INTERACT.API.POOL=( ) BATCH.API.POOL=( ) CICS.API.POOL=( )
8-2
It is possible to specify the same APPLIDs in multiple or all pools, such that an excessive number of APPLIDs are not needed. Note: All DTF nodes do not have to use the same Network Map file; for instance, if you want to communicate with two DTFs with different Network Map contents, you can specify an alternate Network Map in the CICS JCL and in the DTF node record in order to communicate with the second DTF, as long as that DTF is defined as an adjacent node in the Network Map.
!
All Processes to be submitted to a remote DTF facility must reside in the Process library (DD name DMPUBLIB) defined for your CICS system.
Signing On to a Single DTF from Multiple IUI Facilities

Not only can you sign on to multiple DTF facilities from a single CICS IUI, but you can also sign on to a DTF from multiple CICS IUI systems. To sign on to a DTF from multiple CICS IUI systems, note the following:
!
If you are using the DMGSECUR macro to generate your DTF security exit and provide a value for the CICSID keyword at exit generation, all CICS systems accessing that DTF must specify the same CICSID in their signon requests as specified in the CICSID keyword. The password for the CICS signon to a DTF is always CICSIUI. If the CICSID keyword is not specified in the DMGSECUR macro, no checking of CICSIDs for CICS signon requests are performed in the signon exit; however, the CICSID value with a password of CICSIUI are passed to your security facility (if available) or to the Connect:Direct Authorization Facility for validation. The CICSID to be used when signing on to a particular DTF is specified in the CICS DTF NODE configuration record for that DTF. The CICSID equals the userid that is specified on the DTF NODE RECORDS SCREEN. If you let CICSID default at installation time, the value is CICSUSER. For example, CICSID=CICSUSER. Reassemble the supplied security exit for the value to take effect.
If you do not want to use the DMGSECUR macro to generate your DTF security exit, you can recognize the Connect:Direct OS/390 dummy signon by checking the password, which is always CICSIUI. When a dummy signon is received from Connect:Direct OS/390, your security exit returns an Authorization Bit Mask (ABM) of binary zeros. To implement the CICS IUI on a base Connect:Direct that has Stage 2 security turned on, modify the supplied security exit. The exit to be modified depends on which security product is running on the system.
Performing an Immediate or Uncontrolled Shutdown

The CICS IUI facility provides two facilities for orderly termination of the interface, as follows:
! !
Termination is performed automatically by the CICS monitor transaction upon detection of a normal termination of CICS (through a CEMT PERFORM SHUTDOWN command). You can terminate the interface manually by using the CDA transaction.
If you perform an immediate CICS shutdown (through the CEMT PERFORM SHUTDOWN IMMEDIATE command) or if CICS terminates abnormally, you receive system A03 abends from the OS/390 interface. The abends are generated as a result of region termination without detaching all the operating system subtasks created by the CICS IUI facility.
Chapter 8 / Operational Considerations
8-3
In order to avoid the additional abends, you must terminate the CICS IUI facility manually, through the CDA transaction, before you issue the CEMT PERFORM SHUTDOWN IMMEDIATE command.
Restarting Task ABENDS

Administrative options exist to either quiesce (allowing pending requests to complete) or immediately shut down a specific node or the entire CICS Interface. After the shutdown has completed, another administrative option enables you to restart the CICS Interface. In case the entire CICS Interface abends, CICS is notified. The abnormal termination is recorded in the CICS CWA. When the CICS Interface monitor transaction detects that the interface failed, tries to automatically restart the interface. Users with requests to the interface when it crashed are freed by the CICS Interface monitor and the users are sent a message explaining the problem. If a WST abends, then the CST is notified. If any request from a CICS user is pending, CST fills in the return code and message for the user, informing the user that the command might have failed. If the failing WST is the only one running for a node, CST attempts to reattach the WST.
Accessing Accounting and Logging Information

Connect:Direct accounting is accomplished by the DTF. Accounting and statistics are gathered accurately as the DTF enables the userid to be extracted from the UICB for each Connect:Direct command entered. CICS logging is accomplished in the background of CICS operations, but does not record all CICS events and does not duplicate any other Connect:Direct logs. Some events also display on the system console, where major CICS events and errors are reported, such as the following:
! ! ! ! ! ! ! ! ! !
Interface startup CST attach WST attach Node signon of dummy CICS ID WST session failure WST detach CST detach CST termination Administrative commands affecting sessions and requests Return information for CICS users who issue a request and then abnormally exit CICS without waiting for the response
8-4
Using the Extended Submit Facility (ESF)

ESF mode is invoked when an active Connect:Direct OS/390 Connect:Direct DTF session fails or when session establishment fails. In order for Connect:Direct OS/390 to activate ESF, you must install the ESF option on the local DTF and you must enable the option in the configuration file. The user must also include the parameter ESF=YES in the SIGNON command. In ESF mode, a node is available for use only for SUBMIT commands which the user writes directly to the local DTF TCQ file. ESF SUBMIT requests can be issued only by those users who specify ESF as a profile (signon defaults) option.
Specifying Connect:Direct Signon Parameters

Four parameters in the Connect:Direct SIGNON command explicitly support the CICS IUI as follows:
Parameter TYPE=CICS Description Enables a SIGNON command to be embedded in the middle of an API session. This parameter serves no other function and is invalid for a normal signon. Enables specification of the exit to receive control for temporary data set I/O. This parameter is mutually exclusive with the TMPDD, TMPDSN, UNIT, and VOLSER parameters. This exit is called for OPENs, CLOSEs, and WRITEs to the temporary data set. Restricts the number of Connect:Direct statistics. Data is returned from the DTF for the IUI Select Statistics (SS) function. The Connect:Direct API SIGNON (used by CICS WSTs to connect to a Connect:Direct DTF) includes a LIMIT= PARAMETER RECORDS returned by the DTF. The DTF truncates data sent to the Connect:Direct WST API and appends a final record indicating that excessive output is truncated. Enables a SIGNON command to specify the DDNAME of a Connect:Direct Netmap data set which is already allocated.
TDEXIT=modname
TDLIMIT=nnnnn
NETDD=ddname
Understanding Connect:Direct CICS Data Sets

This section lists the data sets used by Connect:Direct DTF and CICS.
Connect:Direct DTF and CICS Data Sets

The following data sets, accessed in read-only mode under CICS, are used by Connect:Direct DTF and the CICS Interface:
Data Set NETMAP Description At least one file exists for each CICS region. The file is defined as a CICS file. It is updated in batch and contains all Connect:Direct nodes available to this CICS environment. Some of the information for the network Connect:Direct nodes is also contained in the configuration file along with additional fields that you can update.
Chapter 8 / Operational Considerations
8-5
Data Set PROCESS
Description One DD name exists for each CICS region. Several files can be concatenated. It is not defined as a CICS file. It is allocated by CICS and used at the subtask level by the Connect:Direct API only. If necessary, you can dynamically allocate and deallocate it using CICS transaction ADYN. One file exists for each system. It is defined as a CICS file and is allocated and opened by CICS. It is updated in batch using the Connect:Direct message load utility. One Transmission Control Queue (TCQ) file exists for each Connect:Direct node. It is not defined as a CICS file. It holds submit (ESF) requests when Connect:Direct DTF is down. It is used at the subtask level by the Connect:Direct API only. It is allocated by CICS and opened by a subtask. If necessary, you can dynamically allocate and deallocate it using the CICS transaction ADYN. One file exists for each Connect:Direct node. It is not defined as a CICS file. It contains VTAM errors written to a sequential file by Connect:Direct and can be routed to SYSOUT under CICS. One file exists for each system. It is defined as a CICS file, and is allocated and opened by CICS. It is updated by the Event Services Support, and is used for restarting ESS. Several files within the Connect:Direct API are dedicated to system trace functions, but are not explicitly used by the CICS Interface. The Connect:Direct API design enables trace data to be written when they are available. To capture trace data, add the appropriate DD name statements to the CICS startup JCL. The files must be present at CICS initialization. Note: Do not dynamically allocate trace files after CICS initializes. Each Connect:Direct API (one per WST) writes trace data to these files when present. An example is NDMCMDS, which you can use to view all commands submitted to the API.
MESSAGE
TCQ
RPLERRCK
EVENT RESTART
Trace Files
Connect:Direct CICS Data Sets

The following data sets, used only by Connect:Direct OS/390, are new for the CICS Interface environment and are updated under CICS:
Data Set CONFIGURATION Description One file exists for each CICS region. It is defined as a CICS file. You can update it online through administrator functions. It is a VSAM KSDS file. It contains all Connect:Direct nodes available to this Connect:Direct OS/390 environment as does NETMAP, but CONFIGURATION contains system parameters that control the Connect:Direct OS/390 environment. One file exists for each CICS region. It is defined as a CICS file that is a VSAM KSDS file with the CICS userid as key. Update it using the signon defaults function and use it to set up auto-signon to Connect:Direct.
USER PROFILE (SIGNON DEFAULTS)
Temporary Data Set

The Connect:Direct API TDEXIT parameter configures the routing of Connect:Direct statistics records to CICS Temporary Storage. CICS Temporary Storage, containing the data, is retained until the user exits the SELECT STATISTICS screen. CICS Temporary Storage containing the data is then deleted.
8-6
Chapter 9
Using the Application Interface
This chapter discusses:

! !
The Connect:Direct OS/390 API Driver Screen The Connect:Direct OS/390 API sample program
Accessing the API Driver Screen

In addition to the Connect:Direct OS/390 IUI, Sterling Commerce provides a facility that enables you to issue standard Connect:Direct commands from a CICS application program. This interface can be used by both terminal and non-terminal tasks. The two typical uses for this API follow:
! !
For terminal tasks, the API enables an installation to provide their own user interface to all or part of Connect:Direct or work with Connect:Direct from application programs. For non-terminal tasks, the API enables an installation to write background transactions which programmatically issue Connect:Direct commands. The most typical sequence is SIGNON - SUBMIT SIGNOFF. In this case, the SIGNON generates a SIGNON TYPE=CICS, and the SIGNOFF results in a cleanup operation of the signon table entry, temporary storage, and so forth. To avoid the requirement of signing on before each command and signing off after each command, the user application can pass a logical task number through the Q012TASK field. If Q012TASK is used, a user program can sign on once and issue multiple commands in pseudo-conversational mode. A sign off need only be issued when the user application is terminating.
An example of the use of this facility is provided in member DMQ247 of the NDMCICS.SAMPLIB. This program enables you to type Connect:Direct commands on a screen and view the resulting return code, message number, message text, and Process number assigned to your Connect:Direct Process. In addition, the name of the CICS Temporary Storage (TS) queue where the results of your command are stored, the count of items in the queue, and the maximum record length in the queue are also displayed. The following components are required to use DMQ247.
Component DMQ247 DMQM98 DMQBMSTB Description The program source, written in assembly language The BMS map used by DMQ247 A parsing macro used by DMQ247
9-2
Component DMQCA012
Description A command-level COMMAREA passed to the CICS Interface
Following is an example of the Connect:Direct API DRIVER screen.

Connect:Direct API DRIVER 10:30:37
COMMAND
____________________________________________ ____________________________________________ ____________________________________________
COMMAND RC COMMAND MSG ID COMMAND MSG PROCESS NUMBER TD EXIT COUNT TS QUEUE NAME TS MAX LRECL EVENT RESTART DATA
PF keys:
3 Exit
5 Signon
6 Command
7 Signoff
Driver Fields
The following table describes the Driver fields:
Field COMMAND COMMAND RC COMMAND MSG ID Description (3-line field) contains your API command. (4-character field) contains the return code from your API Process. (8-character field) contains the identification number of the message associated with your API Process. (64-character field) contains the text of the message. (6-character field) contains the Process number assigned by the system to your API Process.
COMMAND MSG PROCESS NUMBER TD EXIT COUNT
(6-character field) contains the number of bytes indicating how much data is written by the exit module for your API Process. (8-character field) contains the name of the TS queue used during your API request. (4-character field) contains the maximum logical record length in bytes of the TS queue. (62-character field) contains the DATE/TIME/SEQ of the last event record successfully received. Data is only displayed if an EVENT SERVICES CREATE command is issued and a previous event services request had ended abnormally.
TS QUEUE NAME TS MAX LRECL EVENT RESTART DATA
Chapter 9 / Using the Application Interface
9-3
Using the CICS API Option

To use the sample program, you must first change DMQ247 to issue a valid SIGNON command for your environment (the SIGNON command is defined near the end of the source module). Include a valid USERID, PASSWORD, and NODE. Before executing this program as a transaction, you must be signed on to CICS. Also observe the following items.
!
You must then assemble DMQM98 and DMQ247. Sample JCL is in the SAMPLIB. Assemble DMQM98 and DMQ247 as follows:
" "
Use member ASMBMS to assemble DMQM98 Use member ASMCICS to assemble DMQ247
! !
Use the Connect:Direct Administrative (CDA) transaction to verify that the CICS Interface and the appropriate node are both active. The program checks for the presence of a communications area in the Exec Interface Block (EIB). If none is present, or if you press the Clear key, the DMQM98 map is sent and a RETURN TRANSID is performed to invoke the transaction again when you press Enter. If you pressed the PF3 or PF15 key, the program terminates. The DMQM98 map is received. If you pressed PF5 or PF17, a Connect:Direct SIGNON request is generated and the results of the command are presented in the map. Following a successful signon (that is, the return code on DMQM98 after the SIGNON is zero), you can type a valid Connect:Direct command on the line provided in the DMQM98 map and press PF6 or PF18 to send the command to the Connect:Direct DTF. Command results are displayed when they are returned from the DTF. To signoff from the DTF, press PF7 or PF19.
! ! !
When you type a command through the DMQM98 screen, its length is determined and the address of the length and command are placed in the DMQCA012 communications area at label Q012CMDA. Program DMQ012 is then invoked through an EXEC CICS LINK command. When control returns to DMQ247, the DMQCA012 communications area contain the results of the command. Note: The DMQ247 does not actually display the results of the issued command that are stored in CICS temporary storage. You can retrieve these records programmatically or view them using the CICS CEBR transaction. Use the techniques in the DMQ247 sample program to issue any valid Connect:Direct command. Results of commands such as SELECT PROCESS and SELECT STATISTICS are written to CICS temporary storage; other commands can produce no output.
9-4
Linking DMQ012
Access the API by linking program DMQ012 as follows.
EXEC CICS LINK PROGRAM(DMQ012) COMMAREA(Q012COMM) LENGTH(Q012CMLH) +
The COMMAREA Q012COMM is defined by macro DMQCA012 and is also provided in the sample library. A COBOL version of this record layout is provided as member DMQAPIC in the sample library. A brief description of each of the fields follows:
Field Assembler Directive DS Format Description
Q012CMDA
XL4
Full word containing the address of the command to be issued to Connect:Direct. The command must be in the following format: CMDLEN DS H Length of CMDTEXT that Connect:Direct recognizes, not including length of CMDLEN. CMDTEXT DS Clx Command text Return code received after the command is invoked. 0: request completed successfully 1: C:D-CICS interface level error 2: C:D-CICS node level error 3: C:D-CICS signon level error 5: invalid COMMAREA or command passed to CICS API 8 and above: unsuccessful request TDEXIT ITEM COUNT. The field contains the number of records received from the Connect:Direct DTF. TDEXIT MAX ITEM SIZE - the maximum record size received from the Connect:Direct DTF. Process number of the latest submitted Process. Temporary storage ID - the name of the CICS TS queue that contains the command output. Message ID returned from the Connect:Direct OS/390 DTF. Message Text returned from the Connect:Direct OS/390 DTF. Date of the last event acknowledgment. Time of the last event acknowledgment. Sequence number of the last event acknowledgment.
Q012RETC
DS
XL4
Q012TDCT
DS
XL4
Q012TDMX
DS
XL2
Q012PROC Q012TSKY
DS DS
CL6 CL8
Q012MSID Q012MSTX Q012DTE Q012TME Q012SEQ
DS DS DS DS DS
CL8 CL64 PL4 XL4 XL2
Q012CMDA is the only required parameter you must set before linking to DMQ012. For optimum performance, follow the example of DMQ247 and initialize all fields before linking to DMQ012.
Chapter 9 / Using the Application Interface
9-5
Any output generated by issuing the command is returned in a temporary storage queue. Your terminal ID is displayed as the last four characters in the unique TS queue name. Note: DMQ012 requires that it run in CICS key. In CICS versions 3.3 and later, for the transaction that executes a program linking DMQ012, set the following parameters in the CEDA definitions: TaskDataLoc:ANY TaskDataKey:CICS
9-6
Appendix A
CICS Messages
This appendix contains messages that occur during the CICS Interface administrative operations. The following messages are arranged alphabetically: Activate rejected, node is already active - node name This message is displayed if you select option A in the field beside an active node. All values reset from config file This message is displayed if you press Clear. All values reset from signon defaults file This message is displayed if you press Clear to refresh the screen data. CICS USERID required This message is displayed if you pressed Enter with a blank screen present or with no CICS USERID entry present. Control record successfully updated This message is displayed after an edit session when you press PF9. DTF NODE NAME required This message is displayed if you pressed Enter, or PF5, or PF6, with a blank screen. End of file This message is displayed when you scroll forward to the bottom of the file through repeated use of the PF8 key. End of file; values read from config file This message is displayed when you scroll forward to the end of file and then press PF8. End of file; values read from signon defaults file This message is displayed if you press PF8 repeatedly and attempt to access data beyond the end of file. First page This message is displayed if you repeatedly press PF7 and attempt to access data before the beginning of the file. Immediate shutdown rejected; interface is shut. This message is displayed if option I is already selected, and the interface is already inactive.
A-2
Immediate shutdown started This message is displayed if you select option I. The INTERFACE STATUS field changes to INACTIVE. Interface has been started This message is displayed if you select option A and press Enter. Interface is already active This message is displayed if you select option A, and the interface is already active or in the process of starting. Interface must be active to start monitor. This message is displayed if you select option M, and the interface is not active. You must select option A before option M. Last page This message is displayed if you repeatedly press PF8 and attempt to access data beyond the end of the file. Left page This message is displayed if you repeatedly press PF10 and attempt to access data past the left edge of the screen. Line command invalid This message is displayed if you select a different line command other than those defined and press Enter. Monitor has been started. This message is displayed if you select option M. Monitor is already running. This message is displayed if option M is already selected and you select option M again. NETWORK NODE NAME required This message is displayed if you press Enter, or PF5, or PF6, with a blank screen present or with the NETWORK NODE NAME field entry blank. Network node successfully added - node name This message is displayed when the DTF NODE RECORDS screen has your correct data in the fields, and you press PF5. Network node successfully deleted - node name This message is displayed when the DTF NODE RECORDS screen has your correct data in the fields, and you press PF6. No active work queue entries for node node name This message is displayed if you select option W, and no active subtasks are in the work queue. Node activation started, node node name This message is displayed if you select option A in the field beside an inactive node. Node has been restarted - node name This message is displayed in the STATUS ALERT MESSAGE LINE when the NETWORK NODE RECORDS are updated to activate a node.
Appendix A / CICS Messages
A-3
NODE invalid This message is displayed if the node name you typed in is not authorized for signon. NODE required This message is displayed if you pressed Enter on the blank screen without typing in a node name. NODE TYPE invalid This message is displayed if the DTF NODE NAME contains an unacceptable naming convention. No password is currently on file This message is displayed in the Connect:Direct PASSWORD field if you typed an unacceptable or blank Connect:Direct PASSWORD. Normal shutdown rejected; interface is inactive. This message is displayed if already select option S, and you select option S again. Normal shutdown started This message is displayed if you select option S, press Enter. If you press Enter again, the MONITOR TASK NUMBER field changes to NOT RUNNING. No signed-on users This message is displayed if the administrative user selected line command T from the USER STATUS and pressed Enter, thereby terminating the administrative user session. This message is also displayed if you type U from the PRIMARY MENU and no signed-on users of Connect:Direct exist. No users meeting selection criteria This message is displayed if a CICS userid is typed in the CICS USERID field that did not match those users logged on. First, check the USER STATUS screen to see who is logged on for a match. OPTION invalid This message is displayed if you type any OPTION other than a defined option in the OPTION field. Password is on file, but not displayed This message is displayed if you type a Connect:Direct password that is already in the SIGNON DEFAULT record. Past end of file - Prev not available This message is displayed when you scroll backward to the top of the file and then press PF7. PF key invalid This message is displayed if the you press a PF key other than those defined on the screen. Record cannot be deleted, it is not on file This message is displayed if you type in the DTF NODE NAME and then press PF6. No match exists between the DTF NODE NAME and those specified in the configuration file, and therefore the record cannot be deleted. Record cannot be updated, it is not on file This message is displayed if you type in the DTF NODE NAME and then press PF9. No match exists between the DTF NODE NAME and those specified in the configuration file, and therefore the record cannot be updated. Record not found; hit any key when ready. This message is displayed if you type in the DTF NODE NAME and press Enter, but no match exists in the DTF NODE RECORDS screen.
A-4
Right page This message is displayed if you repeatedly press PF11 and attempt to access data past the right edge of the screen. SAFA000I - Connect:Direct signon process completed. This message is displayed if you signed on correctly. SCCS007I - DTF node not active to Connect:Direct CICS. This message is displayed if the node name you typed in is not active in the Connect:Direct system. Check the NODE STATUS screen. SCCS018I - Request could not be assigned to a subtask. This message is displayed if you type in incorrect data or unknown data. The system could not place the signon request in the work queue assigned to the DTF node for the length of time required to complete the signon process. Number of maximum users is exceeded, or incorrect entries in the SIGNON DEFAULTS record caused the failure. Shut immediate started, node node name This message is displayed if you select option I, and you press Enter on an active node. Shut normal started, node node name This message is displayed if you select option N, and you press Enter, on an active node. The STATUS field changes to INACT, and the REQUEST field changes to SHUTNORM. Shut rejected; node already inactive - node name This message is displayed if you select option S and you press Enter on an inactive node. Signon defaults successfully updated - userid This message is displayed if you press PF9 alone or PF9 after an edit session. Start of file This message is displayed if you scroll back to the top of the file through repeated use of the PF7 key. Start of file; values read from config file This message is displayed when the you press PF7 repeatedly to get to the top of the configuration file, then PF8, and then PF7. Start of file; values read from signon defaults file This message is displayed if you press PF7 repeatedly and attempt to access data before the beginning of the file. UNSUPPORTED FUNCTION This message is displayed if the CICS Interface is not started or if you typed in a command unknown to the system. User does not have active work This message is displayed if you select line commands F or C and no active subtask exists in the USER STATUS. USS Command Completed Successfully This message is displayed when the CICS signon is successful.
Appendix A / CICS Messages
A-5
Values read from config file * * * * * This message is displayed if you press PF9. The screen is updated with the values recorded in the configuration file. Note: The following message begins with a variable field and can change as the node names are changed.
node name not NETWORK NODE IN NETMAP specified This message is displayed if you type in the DTF NODE NAME and then press PF5. No match exists between the DTF NODE NAME and those specified in the NETMAP. You must sign on to CICS before using Connect:Direct CICS This message is displayed in the STATUS ALERT MESSAGE LINE if you attempted to sign on using the Connect:Direct or CDA transaction before CICS.
A-6
Glossary
A
ABEND
A task that ends prematurely, or abnormally, due to an error that cannot be resolved by recovery facilities while the task is executing.
ACB
See Access Method Control Block (ACB).
Access Method
A technique for moving data between main storage and input/output (I/O) devices.
Access Method Control Block (ACB)

A control block that links an application program to VSAM or VTAM.
Adapter
A hardware card that allows a device, such as a PC, to communicate with another device, such as a monitor, a printer, or other I/O device. See also Channel-to-Channel Adapter.
ADJACENT.NODE
An entry in the network map. Adjacent node entries define nodes in the network with which the local Connect:Direct may communicate. Each entry specifies a locally used Connect:Direct name, its associated network communications name, and session control parameters for these nodes.
API Pool
Identifies the APPLIDs to be used for API communication with the DTF.
Application Program Interface (API)

The Connect:Direct component that accepts commands from the Interactive User Interface (IUI), Batch Interface, the Operator Interface, or user-written program and places them in a format so that the users request can be executed by the DTF. If there are errors, the API returns a message to the user. If there are no errors, the API sends the command to the DTF using a VTAM session.
APPLID
The name specified in the ACB macro that identifies the application program to VTAM. For Connect:Direct, these APPLIDs correspond to a DTF node name or an API APPLIDs.
Glossary-2
Asynchronous Processes
Processes that occur without a regular or scheduled time relationship. Unexpected or unpredictable with respect to the instructions of the program or to time. Contrast with synchronous.
Attributes
Characteristics or properties that can be controlled, usually to obtain a required appearance; for example, the color of a line.
Authorization File
Connect:Direct file used to control access to Connect:Direct and identify commands that can be executed by user ID. This file can also be used in conjunction with security exit interfaces to support the secured point-of-entry feature.
B
Batch Interface
An interface where non-interactive programs are executed. The environment schedules their execution independently of their submitter. Connect:Direct users issue batch commands using DMBATCH, a Connect:Direct-supplied program.
Buffer
1. 2. A portion of storage used to hold input or output data temporarily. A routine or storage used to compensate for a difference in data rate or time of occurrence of events, when transferring data from one device to another.
Buffer Pool
A set of buffers that contains buffers of the same length.
C
Central Processing Unit (CPU)
The part of a computer that includes the circuits that control the interpretation and execution of instructions.
CF
See Coupling Facility (CF).
Glossary-3
Channel
1. 2. 3. 4. A functional unit, controlled by an S/390 server that handles the transfer of data between processor storage and local peripheral equipment. A path along which signals can be sent. The portion of a storage medium that is accessible to a given reading or writing station. In broadband transmission, a designation of a frequency band 6 MHz wide.
Channel-to-Channel (CTC)
Refers to the communication (transfer of data) between programs on opposite sides of a channel-to-channel adapter (CTCA). The CTCA for Connect:Direct OS/390 can be an ESCON CTC.
Channel-to-Channel Adapter (CTCA)

A hardware device that can be used to connect two channels on the same computing system or on different systems. The CTCA for Connect:Direct OS/390 can be an ESCON CTC.
Checkpoint/Restart
Eliminates the need to retransmit an entire file in the event of a transmission failure. A value on the COPY statement or in the initialization parameter, CKPT.MODE and CKPT, specifies the checkpoint interval. If a copy procedure is interrupted, Connect:Direct will restart that copy at the last checkpoint.
CICS
See Customer Information Control System (CICS).
Command Line Interface

Connect:Direct interface that allows users to submit Connect:Direct Processes and commands from their native command line environment.
Commands
An instruction that directs a control unit or device to perform an operation or a set of operations. Connect:Direct users issue commands to initiate and monitor activity within the Connect:Direct system. Connect:Direct commands can be issued from the IUI, the operator console, a batch job, or a user application program.
Component
1. 2. Hardware or software that is part of a functional unit. A functional part of an operating system; for example, the scheduler or the Hold queue.
Compression
Storing data in a format that requires less space than usual. Data compression is particularly useful in communications because it enables devices to transmit the same amount of data in fewer bits. See also Variable Extended Compression.
Glossary-4
Configuration
The arrangement of a computer system or network as defined by the nature, number, and main characteristics of its functional units. More specifically, the term configuration may refer to a hardware or software configuration. See also System Configuration.
Connect:Direct/Manager
The component of a Connect:Direct/Plex environment that handles the following functions:
! ! ! ! !
Interface connections Statistics file updates CKPT and TCQ/TCX file access TYPE file, AUTH file, NETMAP file, SECURE+ parameter file, and SECURE+ Digital Signature updates Workload balancing
Connect:Direct/Plex
A Connect:Direct system consisting of a Connect:Direct/Manager and one or more Connect:Direct/Servers in a system complex or parallel system complex.
Connect:Direct/Server
A Connect:Direct/Plex component that executes the Processes.
Connect:Direct/Stand-alone Server
A Connect:Direct system that is not part of a Connect:Direct/Plex.
Connectivity
A term used to describe the physical interconnections of multiple devices, computers, or networks employing similar or different technology and/or architecture together to accomplish effective communication between and among connected members. It involves data exchange and/or resource sharing.
Console
A logical device that is used for communication between the user and the system.
Coupling Facility (CF)

A special logical partition (LP) that provides high-speed caching, list processing, and locking functions in Parallel Sysplex.
CPU
See Central Processing Unit (CPU).
Cross-System Coupling Facility (XCF)

An OS/390 facility that allows multiple instances of the same application to communicate and share information with each other.
Glossary-5
CTC
See Channel-to-Channel (CTC).
CTCA
See Channel-to-Channel Adapter (CTCA).
Customer Application
An application that does customer-specific processing.
Customer Information Control System (CICS)

An IBM-licensed program that enables transactions entered at remote terminals to be processed concurrently by user-written application programs. It includes facilities for building, using, and maintaining databases.
D
Daemon
A background task, process, or thread that intermittently awakens to perform some task or function and then returns to an idle state.
DASD
See Direct Access Storage Device (DASD).
Database
1. 2. A set of data, or a part or the whole of another set of data, that consists of at least one file and is sufficient for a given purpose or for a given data-processing system. A collection of data fundamental to a system. See also Database Control (DBCTL), data entry database (DEDB), data sharing, and data sharing group.
Data Set
The major unit of data storage and retrieval, consisting of a collection of data in one of several prescribed arrangements and described by control information to which the system has access.
Data Sharing
In a Parallel Sysplex, the ability of concurrent subsystems or application programs to directly access and change the same data while maintaining data integrity.
Glossary-6
Data Transmission Facility (DTF)

The nucleus component of Connect:Direct. The DTF controls information distribution to other Connect:Direct nodes in the network. Startup parameters that govern the overall activity of the DTF are defined within the initialization parameters. In a Connect:Direct/Plex, the DTF consists of a Connect:Direct Manager and one or more Connect:Direct Servers.
Decipher
To convert enciphered data into clear data.
Decrypt
To convert encrypted data into clear data.
Default
Pertaining to an attribute, value, or option that is assumed when none is explicitly specified.
Direct Access Storage Device (DASD)

A physical device, such as an IBM 3390, in which data can be permanently stored and subsequently retrieved using licensed products like IMS and DB2, or using IBM supported access methods like VSAM in operating system environments like OS/390.
Directory
A list of files that are stored on a disk or diskette. A directory also contains information about the file, such as size and date of last change.
DTF
See Data Transmission Facility (DTF).
Dynamic
Pertaining to an operation that occurs at the time it is needed rather than at a predetermined or fixed time.
E
Execution
The process by which a computer carries out the instruction or instructions of a computer program.
Extended Submit Facility (ESF)

The facility that allows users to queue data transfer requests to a Connect:Direct node that is not active. This allows users to submit work to Connect:Direct, even if the Connect:Direct DTF is down.
Glossary-7
F
File System
The collection of files and file management structures on a physical or logical mass storage device such as a disk.
Format
1. 2. A specified arrangement of things, such as characters, fields, and lines, usually used for displays, printouts, or files. To arrange things such as characters, fields, and lines.
H
Hardware
The physical equipment as opposed to programs, procedures, rules, and associated documentation. Contrast with software.
Host (computer)
1. 2. In a computer network, a computer that provides end users with services such as computation and databases and that usually performs network control functions. The primary or controlling computer in a multiple-computer installation.
I
ICO
See InterConnect Option (ICO).
Initialization
The preparation of a system, device, or program for operation. Connect:Direct initialization parameters specify alternate values for various parameters used during Connect:Direct start up.
Input/Output (I/O)
1. 2. Pertaining to a device whose parts can perform an input process and an output process at the same time. Pertaining to a functional unit or channel involved in an input process, output process, or both, concurrently or not, and to the data involved in such a process.
Interactive
Pertaining to a program or system that alternately accepts input and then responds. An interactive system is conversational; that is, a continuous dialog exists between user and system. Contrast with batch.
Glossary-8
Interactive User Interface (IUI)

An ISPF screen and dialog component that allows users to define and submit Connect:Direct Processes as well as issue Connect:Direct commands that monitor and control administrative and operations activity. An IUI is also available for a CICS environment.
InterConnect Option (ICO)

A feature of Connect:Enterprise. This option provides an automatic, secure way to route application-produced distribution files from a Connect:Direct supported node to a Connect:Enterprise node for distribution, automatically distribute Connect:Enterprise batches to a Connect:Direct node upon arrival, and provide success or failure notification at each process step.
Interface
A shared boundary. An interface might be a hardware component to link two devices or it might be a portion of storage or registers accessed by two or more computer programs.
Interrupt
1. 2. 3. A suspension of a process, such as execution of a computer program caused by an external event, and performed in such a way that the process can be resumed. In data communication, to take an action at a receiving station that causes the sending station to end a transmission. To temporarily stop a process.
I/O
See Input/Output (I/O).
I/O Service Units

A measure of individual data set I/O activity and JES spool reads and writes for all data sets associated with an address space.
IUI
See Interactive User Interface (IUI).
J
Job Entry Subsystem (JES)
A system facility for spooling, job queuing, and managing job-related data.
Glossary-9
L
LAN
See Local Area Network (LAN).
Link
The combination of physical media, protocols, and programming that connects devices.
Load Module
A computer program in a form suitable for loading into storage for execution.
Local Area Network (LAN)

A data network located on the users premises in which serial transmission is used for direct data communication among data stations. It services a facility without the use of common carrier facilities.
Local Cache
A buffer in local system storage that may contain copies of data entries in a CF cache structure.
LOCAL.NODE
An entry in the Network Map. The local node entry defines the logical Connect:Direct name of the local Connect:Direct DTF and its associated communications name. The local node entry also contains the name of the transmission queue and the SUPERUSR ID password, if specified.
Logical Connection
In a network, devices that can communicate or work with one another because they share the same protocol.
Logical Unit (LU)

In VTAM, the source and recipient of data transmissions. Data is transmitted from one logical unit (LU) to another LU. For example, a terminal can be an LU, or a CICS system can be an LU.
Logically Partitioned (LPAR) Mode

A CPC power-on reset mode that enables use of the PR/SM (Processor Resource/Systems Manager) feature and allows an operator to allocate CPC hardware resources (including CPs, central storage, expanded storage, and channel paths) among logical partitions.
LU
See Logical Unit (LU).
Glossary-10 Connect:Direct OS/390 CICS Administration Guide
M
Main Storage
A logical entity that represents the program addressable portion of central storage. All user programs are executed in main storage.
Mainframe (S/390 server)

A large computer, in particular one to which other computers can be connected so that they can share facilities the S/390 server provides, for example, an S/390 computing system to which personal computers are attached so that they can upload and download programs and data.
Memory
The program-addressable storage from which instructions and other data can be loaded directly into registers for subsequent execution or processing.
Migration
Installing a new version or release of a program when an earlier version or release is already in place. See file migration.
Modal Statements
Statements (IF THEN, EIF, ELSE, EXIT, and GOTO) in Connect:Direct that allow you to alter the sequence of Connect:Direct Process execution based on completion of a previous Process step.
Module
A program unit that is discrete and identifiable with respect to compiling, combining with other units, and loading; for example, the input to or output from an assembler, compiler, linkage editor, or executive routine.
Multiprocessing
The simultaneous execution of two or more computer programs or sequences of instructions. See also Parallel Processing.
N
NCP
See Network Control Program (NCP).
Netmap
See Network Map.
Glossary-11
Network
A configuration of data processing devices and software connected for information interchange.
Network Control Program (NCP)

A program residing in a communication controller (for example, the IBM 3745 Communication Controller) that controls the operation of the communication controller.
Network Map
The VSAM file the identifies all valid Connect:Direct nodes and applids in the network. There is one Network Map (netmap) associated with each Connect:Direct node. There is one entry in that netmap for each of the other Connect:Direct nodes to which the local Connect:Direct node can initiate a session. The netmap entries also contain the rules or protocol to which the nodes will adhere when communicating.
Node
1. 2. Any site in a network from which information distribution can be initiated. In SNA, an endpoint of a link or junction common to two or more links in a network. Nodes can be distributed to S/390 server processors, communication controllers, cluster controllers, or terminals. Nodes can vary in routing and other functional capabilities.
O
Offline
Not controlled directly by, or not communicating with, a computer. Contrast with online.
Online
Pertaining to equipment, devices, or data under the direct control of the processor. Contrast with offline.
Online Messages
The completion and error messages that are displayed online.
Operating System (OS)

The software that controls the execution of programs and that may provide services such as resource allocation, scheduling, input/output control, and data management. Although operating systems are predominantly software, partial hardware implementations are possible. Examples are OS/390, VSE/ESA, and VM/ESA.
Operator Interface
Allows Connect:Direct commands to be issued from the operator console. This interface also allows tailoring of Connect:Direct commands through a command list (CLIST) facility.
OS
See Operating System (OS).
P
Parallel
1. Pertaining to a process in which all events occur within the same interval of time, each handled by a separate but similar functional unit; for example, the parallel transmission of the bits of a computer word along the lines of an internal bus. Pertaining to the concurrent or simultaneous operation of two or more devices or to concurrent performance of two or more activities in a single device. Pertaining to the concurrent or simultaneous occurrence of two or more related activities in multiple devices or channels. Pertaining to the simultaneity of two or more processes. Pertaining to the simultaneous processing of the individual parts of a whole, such as the bits of a character and the characters of a word, using separate facilities for the various parts.
2. 3. 4. 5.
Parallel Processing
The simultaneous processing of units of work by many servers. The units of work can be either transactions or subdivisions of large units of work (batch).
Parallel Sessions
The capability of having two or more concurrently active sessions between the same set of two LUs. With parallel session support, Connect:Direct allows multiple, concurrent file transfers between two Connect:Direct nodes.
Parallel Sysplex
A sysplex with one or more coupling facilities.
Partitioned Data Set (PDS)

A data set in DASD storage that is divided into partitions, called members, each of which can contain a program, part of a program, or data.
Partitioned Data Set Extended (PDSE)

A data set organization that stores many different but related members. A PDSE contains an indexed directory and members that are similar to the directory and members of a partitioned data set (PDS) but offers architectural advantages that a PDS cannot. For example, space can be dynamically allocated and reclaimed using PDSEs, exploiting space more efficiently.
Primary Node (PNODE)

The Connect:Direct node on which the Process is being submitted. The primary node may also be referred to as the controlling or source node, but should not necessarily be interpreted as the sending node since PNODE can be the receiver. In every Process, there is one PNODE and one SNODE specified. The submitter of a Process is always the PNODE.
Glossary-13
Process
A series of statements (which can be predefined and stored in a library) submitted through the API to initiate Connect:Direct activity, such as copying files, running jobs, and so on.
Process Statements
The statements that are used to build a Connect:Direct Process. They contain instructions for transferring files, running operating system jobs, executing programs, or submitting other Connect:Direct Processes. Process statements include COPY, RUN JOB, RUN TASK, SUBMIT, SYMBOL, and modals (conditional logic).
Processing Unit
The part of the system that does the processing, and contains processor storage.
Processor
A processing unit, capable of executing instructions when combined with main storage and channels.
Protocol
A specification of the format and relative timing of information exchanged between peer entities within a layer.
R
Record
A set of data treated as a unit.
Recovery
To maintain or regain system operation after a failure occurs. Generally, to recover from a failure is to identify the failed hardware, to de-configure the failed hardware, and to continue or restart processing.
Remote Node
The Connect:Direct node that interacts with the local node during Process execution. The remote node is also referred to as the participating, receiving, target, destination, or secondary node (SNODE).
Resource Access Control Facility (RACF)

The facility that provides access control by identifying and verifying users to the system. RACF authorizes access to resources, logs unauthorized access attempts, and logs accesses to protected data sets.
Response Time
The amount of time it takes after a user presses the enter key at the terminal until the reply appears at the terminal.
Retry Interval
An installation parameter that specifies the interval, in minutes, that the retries mentioned in the Max Retries parameter will be performed.
Routing
The assignment of a path by which a transfer reaches its destination.
S
Secondary Node (SNODE)
The Connect:Direct node that interacts with the primary node (PNODE) during process execution. The secondary node (SNODE) can also be referred to as the participating, target, or destination node. Every Process has one PNODE and one SNODE.
Session
1. 2. 3. 4. 5. 6. The entity through which a Connect:Direct PNODE initiates and executes one or more Processes to one or more SNODEs. The entity through which a Connect:Direct SNODE receives one or more Processes. In SNA, a logical connection between two network addressable units that can be activated, tailored to provide various protocols, and deactivated as requested. The data transport connection resulting from a call or link between two devices. The period of time during which a user of a node can communicate with an interactive system; usually it is the elapsed time between logon and logoff. In network architecture, an association of facilities necessary for establishing, maintaining, and releasing connections for communication between stations.
Session Classes
The installation parameter that specifies the Process class groupings, priorities and number of Processes that can be concurrently executed on this Connect:Direct node.
Shared
Pertaining to the availability of a resource to more than one use at the same time.
SNA
See Systems Network Architecture (SNA).
SNODE
See Secondary Node (SNODE).
SRF
See Sysplex Requester Facility (SRF).
Glossary-15
Standby Connect:Direct Manager

In an extended recovery environment, the backup Connect:Direct Manager that takes over work from the active Connect:Direct Manager when the active Connect:Direct Manager fails.
Standby Connect:Direct Server

In an extended recovery environment, the backup Connect:Direct Server that takes over work from the active Connect:Direct/Server when the active Connect:Direct Server fails.
Standby Connect:Direct System

In an extended recovery environment, the backup Connect:Direct system that takes over work from the active Connect:Direct system when the active system fails.
Statistics Facility
The Connect:Direct facility that records all Connect:Direct activities.
Statistics Files
A pair of VSAM data sets that hold Connect:Direct statistics records to document the history of a Connect:Direct Process.
Storage
A unit into which recorded data can be entered, in which it can be retained and processed, and from which it can be retrieved.
Subsystem
A secondary or subordinate system, or programming support, that is usually capable of operating independently of or asynchronously with a controlling system.
SYMBOL Statement
The Connect:Direct Process statement that allows you to build symbolic substitution values.
Symbolics
The parameters that allow one predefined Process to be used for multiple applications. For example, the file names for a COPY operation could be passed to the Process by the user submitting the Process.
Synchronous
1. 2. Pertaining to two or more processes that depend on the occurrences of a specific event such as common timing signal. Occurring with a regular or predictable timing relationship.
Sysplex
A set of OS/390 systems communicating with each other through certain multisystem hardware components and software services to process workloads.
Sysplex Data Sharing

The ability of multiple OS/390 subsystems to share data across multiple system images. Sysplex data sharing differs from two-way data sharing in that the latter allows sharing across only two system images.
Sysplex Requester Facility (SRF)

A component of Connect:Direct for OS/390 that enables interactive, batch, and application access to DTFs in the system. The SRF runs in an LPAR or on a machine where no DTF is installed. See also Parallel Sysplex and Sysplex Data Sharing.
System
In data processing, a collection of people, machines, and methods organized to accomplish a set of specific functions.
System Configuration
A process that specifies the devices and programs that form a particular data processing system.
Systems Network Architecture (SNA)

A network architecture designed to provide compatibility among a wide variety of hardware and software products so that they can be used to build complex networks. It defines protocols, standards, and message formats to which different hardware and software products must conform. The SNA network consists of network addressable units (NAUs), boundary function components, and the path control network.
T
TCQ
See Transmission Control Queue (TCQ).
TCP/IP
See Transmission Control Protocol/Internet Protocol (TCP/IP).
TDQ
See Transient Data Queue (TDQ).
Terminal
A device that is capable of sending and receiving information over a link; it is usually equipped with a keyboard and some kind of display, such as a screen or a printer.
Glossary-17
Throughput
1. 2. A measure of the amount of work performed by a computer system over a given period of time, for example, number of jobs per day. A measure of the amount of information transmitted over a network in a given period of time.
Transient Data Queue (TDQ)

A CICS temporary storage queue in which event data is stored so that a client application can retrieve the information.
Transmission Control Protocol/Internet Protocol (TCP/IP)

A set of public domain networking protocol standards that specify the details of how computers communicate, as well as a set of conventions for interconnecting networks and routing traffic.
Transmission Control Queue (TCQ)

A VSAM relative record data set (RRDS) used to hold all Processes that have been submitted to Connect:Direct.
V
Variable Extended Compression
The variable compression capability supported by Connect:Direct. This compression will be used when extended compression is specified and both sides support variable compression.
Virtual Storage (VS)

The storage space regarded as addressable main storage by the user of a computer system in which virtual addresses are mapped into real addresses. Virtual storage size is limited by the address scheme of the computer system and the amount of auxiliary storage available, rather than the actual number of main storage locations.
Virtual Storage Access Method (VSAM)

An access method for direct or sequential processing of fixed and variable-length records on direct access devices. The records in a VSAM data set or file can be organized in logical sequence by a key field (key sequence), in the physical sequence in which they are written on the data set or file (entry-sequence), or by relative-record number.
Virtual Telecommunication Access Method (VTAM)

The program that provides for workstation and network control. It is the basis of a System Network Architecture (SNA) network. It supports SNA and certain non-SNA terminals. VTAM supports the concurrent execution of multiple telecommunications applications and controls communication among devices in both single processor and multiple processor networks.
W
Wide Area Network (WAN)
A network that provides communication services to a geographic area larger than that served by a local area network.
X
XCF
See Cross-System Coupling Facility (XCF).
Index
A
A (Activate Interface) option A (Activate) command Abends 8-3 8-3 5-2 5-2 5-2 4-2
CDA transaction
2-1,
8-3 3-6 3-6
CF (Copy File) menu option
Change Signon (SN) menu option CICS API Driver screen CICS ID field 5-3, 9-2
Accounting information Activate (A) command
7-2
ACTIVATE ADMIN REQUEST field Activate Interface (A) option ACTIVE CICS STATUS field ACTIVE TASKS field 4-1 5-1 5-1 4-2 5-2
ADMIN REQUEST field
CICS Interface architecture 1-1 autostart 4-3 components 1-1 control record 3-1 DTF node records 3-1 IUI 8-2 network node records 3-2 CICS PRINTER field CICS STATUS field CICS TERM field 6-2 5-1 7-2
Administration Node Status screen Administration System 2-1
API, See Application Program Interface Application Program Interface (API) 1-1, 4-3, 5-3, Architecture 1-1 8-2 8-1, 9-1, 9-4
5-3, 2-2
CICS TERMID field CICS terminal ID
7-1 2-2, 6-2
CICS USERID field CICSID keyword COMMAND field
Authorization bit mask 3-6, facility 8-2 file 3-6
8-2 9-2 9-2 9-2
COMMAND MSG field 3-4
AUTO.SIGNON field Autostart 4-3
COMMAND MSG ID field COMMAND RC field 9-2
B
Bit Mask 3-6, 8-2
C
C (Configuration) option C (Control record) option 2-2 3-2 7-2 C (Free User and Cancel Users Subtask) command
Commands EXEC CICS LINK 9-3 line 5-1, 7-2 QUIESCE 4-4 SHUTDOWN 4-4, 8-2 SHUTDOWN IMMEDIATE COMMAREA Components 9-2, 1-1 2-2 9-3
8-2
Configuration (C) option
Index-2
Configuration data sets Configuration screen
8-5 3-2
DTF Node Records
3-1 3-3
DTF Node Records (D) option DTF security exit 8-2
Connect:Direct Administration Configuration screen 3-2 Administration Network Node Records screen 3-3 Administration Primary Menu 1-3, 2-1, 3-6 Administration Signon Defaults screen 6-2 Administration User Status screen 7-1 API 5-3, 8-1 Authorization Facility 8-2 commands issuing 9-3 issuing from CICS 9-1 DTF API 4-3 DTF log on 5-1 security exit 3-6 Connect:Direct NODE field 2-2 6-2
DUMMY ID FOR DTF SIGNON field
3-7
E
EIB (Exec interface block) 9-3 3-7 ENTRIES IN WORK QUEUE field Entry fields AUTO.SIGNON 3-4 CICS PRINTER 6-2 CICS USERID 6-2 CICS.TRANSACTION.CODE (ESS) 3-4 CICS.TRANSACTION.CODE (MONITOR) 3-4 CICS.TRANSACTION.CODE (PRINT) 3-4 CICS.TRANSACTION.CODE (STARTUP) 3-4 COMMAND 9-2 COMMAND MSG 9-2 COMMAND MSG ID 9-2 COMMAND RC 9-2 Connect:Direct PASSWORD 6-2 Connect:Direct USERID 6-2 Connect:Direct.EQ.CICSID 3-4 CST.RETRY.INTERVAL 3-5 DEFAULT NODE 6-2 DTF NODE NAME 3-7 DUMMY ID FOR DTF SIGNON 3-7 ENTRIES IN WORK QUEUE 3-7 ESF MODE ALLOWED 6-2 ESF SIGNON ALLOWED 3-7 ESF.RETRY.INTERVAL 3-5 EVENT RESTART DATA 9-2 INACTIVE.INTERVAL 3-5 MAX.SIGNON 3-5 MAX.TASKS 3-5 MAXIMUM WORKER SUBTASKS 3-7 MONITOR.INTERVAL 3-5 NETMAP DDNAME 3-7 NETWORK NODE DESCRIPTION 3-8 NETWORK NODE NAME 3-8 NODE TYPE 3-8 OUTPUT RECORD LIMIT 3-7 PNODE ACCT DATA 6-2 PROCESS NUMBER 9-2 SESSION.RETRY.INTERVAL 3-5 SIGNON.REENTRY 3-4 SKIP.SIGNON.PANEL 3-4 SLOW RESPONSE NOTIFICATION 3-7 SNODE ACCT DATA 6-2
Connect:Direct PASSWORD field Connect:Direct USERID field 6-2
Connect:Direct.EQ.CICSID field Control Record 3-1 3-2 4-3 3-6
3-4
Control Record (C) option Controller Subtask (CST)
Copy File (CF) menu option
Copy File Between Nodes screen CST (Controller Subtask) 3-2,
3-2 4-3 3-5
CST.RETRY.INTERVAL field CURR CMD field CURR TASKS field CURR WORK field 5-3 5-1 5-1
D
D (DTF Node Records) option 3-3 1-1 Data Transmission Facility (DTF) DEFAULT NODE field DMGSECUR macro DMQ012 linking 9-4 9-3 9-3 1-1 5-1, 7-2 8-2 6-2
DMQ247 processing DMQM98 processing
DTF (Data Transmission Facility) DTF NODE NAME field 3-7,
Index-3
Entry fields (continued) STORAGE.SUBPOOL 3-5 SUPPRESS CONNECTION AT STARTUP TD EXIT COUNT 9-2 TS MAX LRECL 9-2 TS QUEUE NAME 9-2 UPPER CASE PRINT 6-2 WORK.RETRY.INTERVAL 3-5 ESF (extended submit feature) mode description 1-1, 4-4 ESF MODE ALLOWED field ESF session 5-3 3-7 3-5 6-2
3-7
ESF SIGNON ALLOWED field ESF.RETRY.INTERVAL field EVENT RESTART DATA EVENT RESTART file 8-5 9-3 3-6 9-2
Exec Interface Block (EIB) Exits Connect:Direct security DTF security 8-2
Extended Submit Feature (ESF) mode description 1-1, 4-4
F
F (Free User) command 7-2 Fields ACTIVE TASKS 4-1 ADMIN REQUEST 5-1 CICS ID 5-3, 7-2 CICS PRINTER 6-2 CICS STATUS 5-1 CICS TERM 5-3, 7-2 CICS TERMID 2-2 CICS USERID 2-2, 6-2 CICS.TRANSACTION.CODE (ESS) 3-4 CICS.TRANSACTION.CODE (MONITOR) 3-4 CICS.TRANSACTION.CODE (PRINT) 3-4 CICS.TRANSACTION.CODE (STARTUP) 3-4 COMMAND MSG ID 9-2 COMMAND RC (return code) 9-2 Connect:Direct NODE 2-2 Connect:Direct PASSWORD 6-2 Connect:Direct USERID 6-2 Connect:Direct.EQ.CICSID 3-4 CST.RETRY.INTERVAL 3-5 CURR CMD 5-3
Fields (continued) CURR TASKS 5-1 CURR WORK 5-1 DEFAULT NODE entry 6-2 DTF NODE NAME 3-7, 5-1, 7-2 DUMMY ID FOR DTF SIGNON 3-7 ENTRIES IN WORK QUEUE 3-7 ESF MODE ALLOWED entry 6-2 ESF SIGNON ALLOWED 3-7 ESF.RETRY.INTERVAL 3-5 EVENT RESTART DATA 9-2 INACTIVE.INTERVAL 3-5 INTERFACE STATUS 4-1 LAST REQUEST 7-2 LAST SIGNON 7-2 LAST TASK# 5-3, 7-2 MAX TASKS 5-1 MAX.SIGNON 3-5 MAX.TASKS 3-5 MAXIMUM WORKER SUBTASKS 3-7 MONITOR TASK MONITOR 4-1 MONITOR.INTERVAL 3-5 MSGID 7-2 NETMAP DDNAME 3-7 NETWORK NODE DESCRIPTION 3-8 NETWORK NODE NAME 3-8 NODE 5-3 NODE TYPE 3-8 OPTION 4-2 OPTION on Primary Menu 2-2 OUTPUT RECORD LIMIT 3-7 PAGE XX OF YY 5-3 PASSWORD MESSAGE 6-3 PENDING REQUEST 4-1 PNODE ACCT DATA entry 6-2 PROCESS NUMBER 9-2 REQUEST DATE/TIME 5-3 SESS TYPE 5-1, 7-2 SESSION DATE/TIME OR SESSION MSGID 5-1 SESSION.RETRY.INTERVAL 3-5 SIGNON.REENTRY 3-4 SKIP.SIGNON.PANEL 3-4 SLOW RESPONSE NOTIFICATION 3-7 SNODE ACCT DATA entry 6-2 STATUS 7-2 STORAGE.SUBPOOL 3-5 SUPPRESS CONNECTION AT STARTUP 3-7 TD CTR 5-3, 7-2 TD EXIT COUNT 9-2 TS MAX LRECL 9-2 TS QUEUE NAME 9-2 UPPER CASE PRINT entry 6-2
Index-4
Fields (continued) USERID 5-3, 7-2 WORK TASK 5-4 WORK.RETRY.INTERVAL
M
M (Start Monitor) option 3-5 Macros 8-2 4-2 Management interface request 4-4 interface subtask 4-4 MAX TASKS field 8-5 MAX.SIGNON field MAX.TASKS field 7-2 5-1 3-5 3-5 3-7
File authorization 3-6 EVENT RESTART 8-5 NETMAP 3-7, 8-1, 8-2 RPLERRCK 8-5 TCQ (Transmission Control Queue) trace 8-5 Free User (F) command 7-2
MAXIMUM WORKER SUBTASKS field MD (Message Display) menu option Menu options Change Signon (SN) 3-6 Copy File (CF) 3-6 Message Display (MD) 3-6 Select Process (SP) 3-6 Select Statistics (SS) 3-6 Signon Defaults (SD) 3-6 Submit Process (SB) 3-6 Menus 1-3, 2-1, 8-5 3-6 3-6 3-6
Free User and Cancel Users Subtask (C) command Free User and Terminate Users Signon (T) command 7-2
I
I (Interface Status) option 2-2 5-2 4-2 I (Shutdown Immediate) command I (Shutdown Interface - Immediate) option INACT CICS STATUS field INACTIVE.INTERVAL field Interactive User Interface (IUI) Interface components 1-2 request management 4-4 startup 4-3 subtask management 4-4 tasks 4-3 VTAM session 4-4 Interface Status (I) option 2-2 4-1 1-1, 8-1, 8-2 5-2 3-5 1-1, 8-1, 8-2
Message data set
Message Display (MD) menu option MESSAGE field 1-3
Mode, Extended Submit Feature (ESF) description MONITOR TASK NUMBER field MONITOR.INTERVAL field MSGID field 7-2 8-1 3-5 4-1
1-1
Multiple Connect:Direct for DTFs signon
INTERFACE STATUS field IUI (Interactive User Interface)
N
N (Network Node Records) option N (Node Status) option NETDD parameter 8-4 3-7 8-2, 8-4 2-2 3-3
L
LAST REQUEST field LAST SIGNON field LAST TASK# field Line commands 7-2 7-2 5-3, 7-2 5-1 7-2
NETMAP DDNAME field NETMAP file Network map 3-7, 4-4 8-1,
5-1,
Log on to Connect:Direct DTF Logging information 8-3
NETWORK NODE DESCRIPTION field NETWORK NODE NAME field Network node records 3-2 3-8
3-8
Index-5
Network Node Records (N) option Network node records screen NODE field 5-3 2-2 3-3
3-3 QUIESCE command 4-4
Q R
REQUEST DATE/TIME field RPLERRCK file 8-5 5-3
Node Status (N) option Node Status screen NODE TYPE field Nodes 2-2 5-1 3-8
O
OPTION fields 2-2, 4-2 Options Activate Interface (A) 4-2 Configuration (C) 2-2 Control Record (C) 3-2 DTF Node Records (D) 3-2 Interface Status (I) 2-2 Network Node Records (N) 3-2 Node Status (N) 2-2 Shutdown Interface - Immediate (I) 4-2 Shutdown Interface - Normal (S) 4-2 Signon Defaults (S) 2-2 Start Monitor (M) 4-2 User Status (U) 2-2 OUTPUT RECORD LIMIT field 3-7
S
S (Shutdown Interface - Normal) option S (Shutdown normal) command S (Signon Defaults) option 2-2 3-6 5-2 4-2
SB (Submit Process) menu option
Screens Administration Configuration 3-2 Administration Network Node Records Administration Node Status 5-1 Administration Signon Defaults 6-2 Administration User Status 7-1 Copy File Between Nodes 3-2 SD (Signon Defaults) menu option Security exit Connect:Direct DTF 8-2 3-6 3-6 3-6 3-6
3-3
P
PAGE XX OF YY field Parameters API IOEXIT 8-5 SIGNON 8-4 PASSWORD MESSAGE field PENDING REQUEST field PF keys PNODE 1-4 5-1 6-2 6-3 5-3
Select Process (SP) menu option Select Statistics (SS) menu option SESS TYPE field 5-1, 7-2
SESSION DATE/TIME OR SESSION MSGID field 5-1 Session manager 1-1 3-5
4-1
SESSION.RETRY.INTERVAL field Shutdown command 4-4, 8-2
Shutdown Immediate (I) command
5-2,
8-2 4-2
PNODE ACCT DATA entry field PRIM SESS TYPE field Primary menus Process data set 1-3, 8-5 9-2 5-2 2-1, 3-6
Shutdown Interface - Immediate (I) option Shutdown Interface - Normal (S) option Shutdown normal (S) command 5-2 5-2
4-2
SHUTIMM ADMIN REQUEST field SHUTNORM ADMIN REQUEST field Signon Defaults (S) option 2-2
PROCESS NUMBER field
5-2
Signon Defaults (SD) menu option
3-6
Index-6
Signon Defaults screen SIGNON parameters
6-2 8-4 3-4 3-4 3-7
User Profile (Signon Defaults) data sets User Status (U) option User Status screen USERID field 5-3, 7-1 7-2 2-2
8-5
SIGNON REENTRY field
SKIP.SIGNON.PANEL field
SLOW RESPONSE NOTIFICATION field SN (Change Signon) menu option SNODE ACCT DATA field 6-2 3-6 3-6 3-6
V
Virtual Telecommunications Access Method (VTAM) 1-1, 4-2, 4-4
SP (Select Process) menu option SS (Select Statistics) menu option Start first task command Start Monitor (M) option Startup 4-3 7-2 3-5 5-2 4-2
W
W (Work queue display) command Work queue display (W) command WORK TASK field 5-4 3-5 5-2 5-2
STATUS field
WORK.RETRY.INTERVAL field Worker Subtask, see WST 3-6 WST definition 3-2, 4-2 setting maximum 3-7 specifying inactive time
STORAGE.SUBPOOL field
Submit Process (SB) menu option Subtask management 4-4
SUPPRESS CONNECTION AT STARTUP field System fields 1-3
3-7
3-5
T
T (Free User and Terminate Users Signon) command 7-2 TCQ (Transmission Control Queue) TD CTR field 5-3, 7-2 9-2 1-1, 8-5
TD EXIT COUNT field TDEXIT parameter TDLIMIT parameter TIME field Trace files 1-3 8-5 8-4
8-4
Transient Data Counter (TD)
5-3,
7-2 1-1, 8-5
Transmission Control Queue (TCQ) TS MAX LRECL field TS QUEUE NAME field TYPE parameter 8-4 9-2 9-2
U
U (User Status) option 2-2 6-2 UPPER CASE PRINT field

C Ics Admin Guide

Uploaded by

Copyright:

Available Formats

C Ics Admin Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

C Ics Admin Guide

Uploaded by

Copyright:

Available Formats

PN 00734

CICS Administration Guide

About the CICS Interface

Accessing the Primary Menu

Maintaining Configuration Information

Connect:Direct OS/390 CICS Administration Guide

3-6 3-7 3-7 3-8

Working with the Administration Interface

Viewing Node Status

Maintaining Signon Defaults

Viewing User Status

8-4 8-4 8-4 8-4 8-5 8-5

Using the Application Interface

Appendix A Glossary Index

Connect:Direct OS/390 CICS Administration Guide

Connect:Direct OS/390 CICS Administration Guide

Connect:Direct OS/390 Documentation

Getting Support for Sterling Commerce Products

Connect:Direct OS/390 CICS Administration Guide

About the CICS Interface

Data Transmission Facility (DTF) Extended Submit Feature (ESF) Mode

Introduction to the Administration System

Connect:Direct OS/390 CICS Administration Guide

Components of the CICS Interface

Connect: Direct OS/390 CICS API

Connect:Direct DTF Session Mgr DTF Session Mgr

DTF Session Mgr

Connect: Direct DTF API VTAM

Connect: Direct DTF 1

Connect: Direct DTF 2

Connect: Direct DTF 3

Connect: Direct DTF 4

Local and Cross Domain DTF Sessions

Local Node DTF Configuration ESF or Primary DTF Session

Multi-Session Cross Domain DTF Signon

Single Session Cross Domain DTF Signon

Interrupted Session Management

Chapter 1 / About the CICS Interface

Structure of the Administration System

DTF Node Records

Network Node Records

Administration Screen Features

System and Data Fields

Connect:Direct OS/390 CICS Administration Guide

Accessing the Primary Menu

Using the Administration System

Using the Primary Menu

... ... ... ... ...

Connect:Direct OS/390 CICS Users Guide

Maintaining Configuration Information

Control Record DTF Node Records Network Node Records

DTF Node Records

Connect:Direct OS/390 CICS Administration Guide

Network Node Records

Accessing the Administration Configuration Screen

Chapter 3 / Maintaining Configuration Information

Updating the Control Record

HHMMSS MMSS HHMMSS MMSS SS HHMMSS 01-99 002-127

Connect:Direct OS/390 CICS Administration Guide