Ars User Guide

PN 00738
Connect:Direct OS/390
Activity Reporting System Users Guide
PN 00738
Connect:Direct OS/390
Activity Reporting System Users Guide
Version 4.4
Connect:Direct OS/390 Activity Reporting System Users 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 1984, 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.
CDARSUG403
Contents
Preface
Chapter Overview ................................................................................................................. Connect:Direct OS/390 Documentation ............................................................................... Getting Support for Sterling Commerce Products ................................................................ v vi vii
Chapter 1
About the Activity Reporting System

Using Activity Reports.......................................................................................................... ARS and Connect:Direct....................................................................................................... Requesting ARS Reports ............................................................................................... System Prerequisites ............................................................................................................. Business Solutions Using ARS ............................................................................................. 1-1 1-1 1-2 1-2 1-2
Chapter 2
ARS Report Examples

Connect:Direct Activity Report ............................................................................................ Connect:Direct Summary Report.......................................................................................... Connect:Direct Exception Report ......................................................................................... Connect:Direct Security Violations Report .......................................................................... Connect:Direct Function Reports.......................................................................................... Connect:Direct NonPDS Copy Report .......................................................................... Connect:Direct PDS Copy Report ................................................................................. Connect:Direct Run Job Report ..................................................................................... Connect:Direct Run Task Report................................................................................... Connect:Direct Submit Within a Process Report .......................................................... 2-1 2-3 2-5 2-7 2-8 2-8 2-10 2-13 2-14 2-15
iv
Connect:Direct OS/390 Activity Reporting System Users Guide
Chapter 3
Requesting ARS Reports Using Screens

Step 1Requesting Reports Using ARS Screens................................................................... Accessing the ARS Screens Using the Connect:Direct Interactive Interface (IUI)....... Accessing the ARS Screens ........................................................................................... ARS Report Options Screen........................................................................................... ARS Connect:Direct Requirements Screen ................................................................... ARS SAS Requirements Screen..................................................................................... Displayed Job Stream Created from Screens ................................................................. Step 2Running the Job......................................................................................................... 3-1 3-2 3-3 3-3 3-5 3-6 3-7 3-7
Chapter 4
Requesting Multiple ARS Reports or Scheduled Processing

Sample Job Stream ................................................................................................................ Modifying the Sample Job Stream ................................................................................. Job Stream Definitions ................................................................................................... Sample Connect:Direct Process That Submits Job Stream............................................ Routing Multiple Reports to an Output Data Set ........................................................... 4-2 4-2 4-3 4-5 4-5
Chapter 5
ARS Record Layouts

Description of an SAS Variable ............................................................................................ Authorization Event Record.................................................................................................. Change Process Termination Record .................................................................................... Copy Termination Record ..................................................................................................... Delete Process Termination Record ...................................................................................... Display Statistics Record....................................................................................................... Flush/Suspend Process Termination Record......................................................................... PDS Member Copy Record ................................................................................................... Process Submit Statistics Record .......................................................................................... Process Termination Record ................................................................................................. Run Job Termination Record ................................................................................................ Run Task Termination Record .............................................................................................. Signon/Signoff Statistics Record........................................................................................... Start Connect:Direct Command Record................................................................................ Stop Connect:Direct Statistics Record .................................................................................. Stop Session Statistics Record .............................................................................................. Write to Operator (WTO) Statistics Record.......................................................................... 5-2 5-2 5-3 5-4 5-7 5-7 5-8 5-9 5-10 5-11 5-12 5-13 5-14 5-14 5-15 5-15 5-16
Glossary Index
Preface
This manual explains how to use the Activity Reporting System (ARS) in conjunction with Connect:Direct OS/390. ARS produces reports of Connect:Direct activity. Connect:Direct writes the ARS reports using the SAS System, by SAS Institute, Inc. The first chapter in the book introduces you to the basic components and general concepts of ARS, which gives you general knowledge about the product. This guide assumes knowledge of the IBM OS/390 operating system, including its applications, network, and environment. If you are not familiar with the IBM OS/390 operating system, refer to the IBM OS/390 library of manuals. The following topics are also discussed in this manual:
! ! ! ! !
Introduction to ARS ARS report examples Requesting ARS reports using ARS screens Requesting ARS reports through Connect:Direct Processes or through a predefined batch job stream that is run by a job scheduling subsystem Field descriptions for each Connect:Direct statistics record
Chapter Overview
The organization of the Connect:Direct OS/390 Activity Reporting System Users Guide follows:
! ! ! ! ! !
Chapter 1, About the Activity Reporting System, describes Connect:Direct, the Activity Reporting System, system prerequisites, and business solutions. Chapter 2, ARS Report Examples, describes the reports available from ARS. Chapter 3, Requesting ARS Reports Using Screens, describes the use of the interactive interface in requesting reports. Chapter 4, Requesting Multiple ARS Reports or Scheduled Processing, describes methods for scheduling processing and requesting multiple reports. Chapter 5, ARS Record Layouts, lists the information you need to customize ARS reports. The Glossary defines Connect:Direct terms used in this manual.
vi
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
vii
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.
viii
Chapter 1
About the Activity Reporting System
Connect:Direct links technologies and moves all types of information between networked systems and computers. It manages high-performance transfers by providing such features as: automation, reliability, efficient use of resources, application integration, and ease of use. Connect:Direct software offers choices in communications protocols, hardware platforms, and operating systems. It provides the flexibility to move information among mainframes, midrange systems, desktop systems, and LAN-based workstations.
Using Activity Reports

The Activity Reporting System (ARS) produces reports of Connect:Direct activity. While Connect:Direct itself produces statistics, ARS enables you to access more information and also provides sorting capabilities. You can request ARS reports in three ways:
! ! !
Make requests through ARS screens using IBM Time Sharing Option/Interactive System Productivity Facility (TSO/ISPF) Request reports automatically through a Connect:Direct Process Schedule a batch job through a job scheduling subsystem
With ARS, you do not have to pass data to OS/390 system management facilities (SMF) or write SAS requests to print Connect:Direct activity reports. Use ARS as a standard reporting format throughout a network for tracking Connect:Direct activity.
ARS and Connect:Direct

Connect:Direct automatically collects statistical data about Connect:Direct activity and stores it in a data set. ARS can access this statistical data and produce the following reports for a selected time period:
! ! ! !
Connect:Direct Activity Report lists activity by Process step Connect:Direct Summary Report summarizes all activity Connect:Direct Exception Report lists all Process steps that do not complete successfully Connect:Direct Security Violations Report lists security violations by signon security failures, Process security failures, and data set access security failures
1-2
Connect:Direct Function Reports provides the activity reports for the following types of Process steps:
" " " " "
Nonpartitioned Data Set (PDS) COPY PDS COPY RUN JOB RUN TASK Submit Within a Process
Requesting ARS Reports

Following are two methods for requesting ARS reports:
! !
Through the ARS screens where you can create a job stream that requests reports. The screens automatically build the job or allow you to edit the sample report job stream. By using the sample JCL member that is provided with ARS.
System Prerequisites
The following product releases are required:
! !
Any release of Connect:Direct OS/390. SAS base running under OS/390. ARS was tested using Release 6.09 of SAS. Note: Connect:Direct OS/390 must be active in order to run ARS.
Business Solutions Using ARS

ARS is designed to provide data center management with additional tools to monitor and track Connect:Direct usage. Use the information in the reports to track attempted security violations, analyze capacity planning related data, examine Connect:Direct utilization, and isolate failed Connect:Direct Processes. The following table describes how you can use ARS.
Function Data Center Management Description The data center manager wants to keep track of Connect:Direct activities performed. The Connect:Direct Activity Report lists all of the Process steps that occurred in this data center during a specified time period. The Connect:Direct NonPDS Copy Report and Connect:Direct PDS Copy Report provide additional information on all COPY steps performed. A system administrator requests a listing of any Connect:Direct-related security violations on a daily basis. The Connect:Direct Security Violations Report lists the following violations: Sign on security failures Processes not run due to lack of authorization Data set access security violations
Security Violations
Chapter 1 / About the Activity Reporting System
1-3
Function Capacity Planning
Description The capacity planner at a data center needs to know how many bytes are transferring between this data center and other data centers and the total transmission times. The Connect:Direct Summary Report provides this type of information by remote data center for a specified time period.
Connect:Direct Utilization
The data center administrator studies Connect:Direct utilization by examining how many application programs are submitted or invoked using Connect:Direct. The administrator uses this information with a job scheduling system to produce a comprehensive analysis of all jobs run at a data center. Two ARS reports provide this type of utilization summary. The Connect:Direct Run Job Report provides information about all jobs submitted by Connect:Direct. The Connect:Direct Run Task Report provides information about all programs executed under the control of Connect:Direct. The Connect:Direct Exception Report is an excellent tool for researching why a Process does not run. This report lists each failed Process for a requested time period along with the reason for the failure.
Problem Isolation
1-4
Chapter 2
ARS Report Examples
This chapter explains the types of ARS reports available. The reports are as follows:
! ! ! ! !
Connect:Direct Activity Report Connect:Direct Summary Report Connect:Direct Exception Report Connect:Direct Security Violations Report Connect:Direct Function Reports:
" " " " "
Connect:Direct NonPDS Copy Report Connect:Direct PDS Copy Report Connect:Direct Run Job Report Connect:Direct Run Task Report Connect:Direct Submit Within a Process Report
You can request these reports in the following ways:

! ! !
Through ARS screens using TSO/ISPF Through a Connect:Direct Process that is defined to automatically request reports Through a pre-defined batch job stream that is run by a job scheduling subsystem
Connect:Direct Activity Report

The Connect:Direct Activity Report lists Connect:Direct activity by Process step. The ARS software sorts the steps for each secondary node (SNODE) location by userid and then by Process number, for a specified time period.
2-2
You can specify the start date and time and the stop date and time. Following is an example of the Connect:Direct Activity Report.
Connect:Direct ACTIVITY REPORT (ARS00001) 17:12 WEDNESDAY, JUNE 24, 1998 1 NODE = CD.BOSTON ------------------------------------------------------SNODE=CD.BOSTON-----------------------------------------------USERID PROC PROC STEP FUNCTION ELAPSE PNODE CC EXC MSG DATE # NAME NAME TIME ID ALPHA 46 COPY1 STEP01 COPY 0:00:01.89 CD.BOSTON 00000000 SCPAOO0I 06/17/1998 ALLEN 63 COPY2 STEP01 COPY 0:00:02.08 CD.CHICAGO 00000000 SRPA000I 06/17/1998 BETA 87 RUNJOB LAB RUNJOB 0:00:01.26 CD.CHICAGO 00000000 SRJAOOOI 06/17/1998 ETHAN 89 RUNJOB SUBSTEP RUNJOB 0:00:00.68 CD.JERSEY 00000000 SSJA000I 06/17/1998 LEWIS 9 RUNT STEP1 RUNTASK 0:00:00.11 CD.JERSEY 00000000 SRTA000I 06/17/1998 LOUIS 95 SUB SUBSTEP SUBMIT 0:00:01.34 CD.JERSEY 00000008 SSUBOOI 06/17/1998 MULLEN 96 COPY05 STEP1 COPY 0:00:01.57 CD.MIAMI 80013000 SCPA000I 06/17/1998 WARD 99 COPY05 STEP1 COPY 0:00:02.06 CD.MIAMI 80806000 SCPAOOOI 06/17/1998 WARREN 379 SUB SUBSTEP SUBMIT 0:00:00.96 CD.MIAMI 00000008 *** SSUB005I 06/17/1998 ------------------------------------------------------SNODE=CD.JERSEY-----------------------------------------------JONES 544 RUNT STEP1 RUNTASK 0:00:00.18 CD.BOSTON 80806000 *** SRTA004I 06/18/1998 ------------------------------------------------------SNODE=CD.MIAMI------------------------------------------------USERID PROC PROC STEP FUNCTION ELAPSE PNODE CC EXC MSG DATE # NAME NAME TIME ID ALLEN ALLEN BURNS BURNS GEORGE JONES LISA MILLER RYAN RYAN RYAN RYAN SMITH SMITH TURNER WARREN 413 414 415 418 420 421 422 425 426 427 428 429 430 431 432 433 COPY05 RUNTASK RUNT SUB PDSCOPY PDSCOPY RUNJOB RUNT SUB RUNJOB RUNJOB RUN10 RUN20 SUBACCT SUBSTAT SUBSALE COPY01 LABRNJ2 STEP1 SUBSTEP COPY01 COPY01 LABRNJ2 STEP1 SUBSTEP LABRNJ2 LABRNJ2 STEP1 STEP1 SUBSTEP SUBSTEP SUBSTEP COPY RUNJOB RUNTASK SUBMIT COPY COPY RUNJOB RUNTASK SUBMIT RUNJOB RUNJOB RUNTASK RUNTASK SUBMIT SUBMIT SUBMIT 0:00:06.96 0:00:01.13 0:00:00.28 0:00:01.79 0:00:05.42 0:00:03.21 0:00:00.34 0:00:00.18 0:00:00.68 0:00:00.39 0:00:01.54 0:00:00.25 0:00:00.09 0:00:01.19 0:00:01.59 0:00:02.47 CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON CD.BOSTON 00000000 00000000 00000000 00000000 00000000 00000008 80013000 80806000 00000008 80013000 00000000 80806000 00000000 00000004 00000008 00000000 SCPAOO0I SRJA000I SRTAOOOI SSUB000I SCPA000I SDE5078I SVGS010I SRTAOO4I SSUB005I SVSG010I SRJA000I SRTA004I SRTA000I SBPA016I SPQG002I SSUB000I 06/17/1998 06/17/1998 06/17/1998 06/17/1998 06/17/1998 06/17/1998 06/17/1998 06/17/1998 06/17/1998 06/19/1998 06/19/1998 06/19/1998 06/19/1998 06/19/1998 06/19/1998 06/19/1998
*** *** *** *** *** *** *** *** *** ***
The following table contains a description of the report fields.

Report Field NODE SNODE USERID PROC # PROC NAME STEP NAME FUNCTION Description Connect:Direct node where the statistics file is being examined. Connect:Direct secondary node. Connect:Direct userid. Connect:Direct Process number. Connect:Direct Process name. Name (or label) assigned to the Process step. Connect:Direct activity. Valid Process steps are COPY, RUN JOB, RUN TASK, and SUBMIT (within a Process). Function duration time in hh:mm:ss.hh format. Connect:Direct primary node. Connect:Direct completion code in hexadecimal format. Exception field is displayed *** when a Process step does not complete successfully. Connect:Direct message ID. Date Connect:Direct activity began. Date format is mm/dd/yyyy. Process start date does not conform to the DATEFORM initialization parameter.
ELAPSE TIME PNODE CC EXC MSG ID DATE
Chapter 2 / ARS Report Examples
2-3
Connect:Direct Summary Report

The Connect:Direct Summary Report summarizes activity for the node containing the statistics file being examined. The report categorizes Connect:Direct activity by SNODE for a specified time period. The conclusion of the report includes a summary for all SNODEs. Information includes:
! ! ! ! ! ! ! ! ! ! ! !
Total Process steps run Total COPY steps run Total RUN JOB steps run, and RUN JOB steps submitted at this node Total RUN TASK steps run, RUN TASK steps executed at this node Total SUBMIT (within a Process) steps run and number of Processes submitted at this node Number of successful steps and unsuccessful steps Total bytes tested, written, sent, and received by this node Total elapsed time for all Process steps in this time period Average time to complete a Process step Total elapsed time for all COPY steps Average time to complete a COPY step Effective send and receive rates
You can specify the start date and time and the stop date and time. Following is an example of the Connect:Direct Summary Report
CD SUMMARY REPORT (ARS00002) NODE = CD.JERSEY SNODE = ALL SNODES FIRST FUNCTION BEGAN EXECUTING ON 06/17/1998 AT 10:07:03.28 LAST FUNCTION FINISHED EXECUTION ON 07/10/1998 AT 11:26:42.75 66 PROCESS STEPS WERE COMPLETED FOR THIS TIME PERIOD. 51 TOTAL COPY STEPS OR 77.3 % OF TOTAL STEPS RUN WERE COPIES 9 TOTAL RUNJOB STEPS OR 13.6 % OF TOTAL STEPS RUN WERE RUNJOBS 6 RUNJOBS WERE SUBMITTED ON CD.JERSEY 3 TOTAL RUNTASK STEPS OR 4.5 % OF TOTAL STEPS RUN WERE RUNTASKS 2 RUNTASKS WERE ATTACHED ON CD.JERSEY 3 TOTAL SUBMIT STEPS OR 4.5 % OF TOTAL STEPS RUN WERE SUBMITS 2 SUBMITS (WITHIN A PROCESS) ON CD.JERSEY 48 SUCCESSFUL STEPS OR 72.7 % OF TOTAL STEPS RUN COMPLETED WITH A ZERO RETURN CODE 18 UNSUCCESSFUL STEPS OR 27.3 % OF TOTAL STEPS RUN COMPLETED WITH A NON-ZERO RETURN CODE 13:22 FRIDAY, JUNE 19, 1998 2 CD SUMMARY REPORT (ARS00002) NODE = CD.JERSEY SNODE = ALL SNODES 28,001,880 TOTAL BYTES WERE READ 28,019,820 TOTAL BYTES WERE SENT 28,250,480 TOTAL BYTES WERE WRITTEN 28,269,124 TOTAL BYTES WERE RECEIVED 0:26:23.98 WAS THE TOTAL FUNCTION TIME (SPENT PERFORMING FUNCTIONS) 0:00:24.00 WAS THE AVERAGE TIME TO COMPLETE A FUNCTION 0:26:06.91 WAS THE TOTAL COPY TIME (SPENT TRANSFERRING DATA) 0:00:30.72 WAS THE AVERAGE TIME TO COMPLETE A COPY 17.999 BYTES/SECOND = EFFECTIVE SEND RATE 18.16 BYTES/SECOND = EFFECTIVE RECEIVE RATE

Report Field NODE SNODE Description Connect:Direct node where the statistics file is being examined. Connect:Direct secondary node.
2-4
Report Field FIRST FUNCTION
Description Actual date/time that first Process step began executing during specified time period. Includes any step that started before specified time, but is under way or completes during the time period. Actual date/time last Process step finished executing during specified time period. If a step started during specified time period but ended after requested stop time or stop date, it is not included in this report. Total number of Process steps completed in time period. Total number of COPY steps run. Percentage of total steps run that are COPY steps.
LAST FUNCTION
PROCESS STEPS COMPLETED TOTAL COPY STEPS % TOTAL STEPS RUN WERE COPIES TOTAL RUNJOB STEPS % TOTAL STEPS RUN WERE RUNJOB # RUNJOBS SUBMITTED TOTAL RUNTASK STEPS % TOTAL STEPS RUN WERE RUNTASKS # RUNTASKS ATTACHED TOTAL SUBMIT STEPS % TOTAL STEPS RUN WERE SUBMITS # SUBMITS (WITHIN A PROCESS) SUCCESSFUL STEPS % OF TOTAL STEPS RUN WITH ZERO RETURN CODE UNSUCCESSFUL STEPS % OF TOTAL STEPS RUN WITH NON-ZERO RET CD TOTAL BYTES WERE READ TOTAL BYTES WERE SENT TOTAL BYTES WERE WRITTEN TOTAL BYTES WERE RECEIVED WAS TOTAL FUNCTION TIME
Total number of RUN JOB steps run. Percentage of total steps run that are RUN JOB steps.
Number of RUN JOB steps submitted to run at NODE. Total RUN TASK steps run. Percentage of total steps run that are RUN TASK steps.
Number of RUN TASK steps that are attached on NODE. Total number of SUBMIT steps run. Percentage of total steps run that are SUBMIT (within a Process) steps.
Number of SUBMIT (within a Process) steps submitted to run at NODE.
Total number of successful steps. Percentage of total successful steps.
Total number of unsuccessful steps. Percentage of total unsuccessful steps.
Total number of bytes read by NODE. Total number of bytes sent by NODE. Total number of bytes written by NODE. Total number of bytes received by NODE. Sum of elapsed times of all individual Process steps. The elapsed time for this calculation is the time period between when the step started and when the step completed. Total function time divided by number of Process steps run.
WAS AVERAGE TIME TO COMPLETE A FUNCTION WAS TOTALCOPY TIME
Sum of elapsed times for all individual COPY steps. The elapsed time for this calculation is the time period between when the step started and when the step completed.
2-5
Report Field WAS AVERAGE TIME TO COMPLETE A COPY EFFECTIVE SEND RATE
Description Total COPY time divided by the total number of COPY steps run.
Total bytes sent divided by elapsed time. For this calculation, the elapsed time is the time between when the first COPY step in the data set began and the last COPY step in the data set completed. Total bytes received divided by elapsed time. For this calculation, the elapsed time is the time between when the first COPY step in the data set began and the last COPY step in the data set completed.
EFFECTIVE RECEIVE RATE
Connect:Direct Exception Report

The Connect:Direct Exception Report lists Process steps that does not complete successfully for a specified time period. The ARS software sorts Process steps by SNODE, by userid, and then by Process number. Each item in this report displays information unique to the executed Process step. For example, the type of information that is displayed for a failed COPY step differs from that of a failed RUN TASK step. A summary of all exception cases is listed at the conclusion of the report.
17:12 WEDNESDAY, JUNE 24, 1998 1 CD EXCEPTION REPORT (ARS00003) NODE = CD.BOSTON USERID PROC * PROC NAME STEP NAME EXCEPTION INFORMATION ****** ******* ********* ********* ******************************************************************* BYRAN 424 NONCOPY COPY01 ** NON-PDS COPY ** 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 00000008 MSG ID = SDE5708I SENDING NODE ==> CD.JERSEY SRC DSNAME ==> USERHLQ.NONPDS RECEIVING NODE ==> CD.BOSTON DEST DSNAME ==> USERHLQ.NEWNONPDS CATALOG ERROR: CATALOG STRUCTURE OR NEW REQUEST FAILED ----------------------------------------------------------------------------------------------------------JONES 421 PDSCOPY COPY01 ** PDS COPY ** 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 00000008 MSG ID = SDE5708I SENDING NODE ==> CD.JERSEY SRC DSNAME ==> USERHLQ.TESTPDS RECEIVING NODE ==> CD.BOSTON DEST DSNAME ==> USERHLQ.NEWPDS CATALOG ERROR: CATALOG STRUCTURE OR NEW REQUEST FAILED ----------------------------------------------------------------------------------------------------------MILLER 425 RUNJOB LABRNJ2 ** RUNJOB ** 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 80013000 MSG ID = SVSG010I DATASET CONTAINING JOB = USERHLQ.CNTLIMEMBER INTENDED NODE FOR JOB SUBMISSION = CD.BOSTON NON-VSAM OPEN ERROR OCCURRED ----------------------------------------------------------------------------------------------------------SMITH 479 RUNT STEP1 ** RUNTASK ** 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 80806000 MSG ID = SRTA004I PROGRAM NAME = ABCNAME INTENDED NODE FOR PROGRAM EXECUTION = CD.JERSEY CD-OS/390 RUN TASK CANNOT FIND SPECIFIED TASK IN STEP LIBRARY ----------------------------------------------------------------------------------------------------------WARD 499 SUB SUBSTEP ** SUBMIT ** 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 00000008 MSG ID = SSUB005I DATASET CONTAINING PROCESS = THERE IS NO SUCH LIBRARY AS THIS.(NOEXIST) INTENDED NODE FOR PROCESS SUBMISSION = CD.JERSEY UNABLE TO ALLOCATE DSN SPECIFIED IN SUBMIT STATEMENT 17:12 WEDNESDAY, JUNE 24, 1998 (ARS00003) 3
CD EXCEPTION REPORT NODE = CD.BOSTON
SUMMARY INFORMATION ************************** 9 NON-SUCCESSFUL STEPS IN 17 PROCESS STEPS RUN OR --> 52.9 % OF TOTAL PROCESS STEPS RUN COMPLETED WITH A NON-ZERO RETURN CODE 1 NON-SUCCESSFUL COPIES OF 3 COPY STEPS RUN OR --> 33.3 % OF TOTAL COPY STEPS RUN COMPLETED WITH A NON-ZERO RETURN CODE 2 NON-SUCCESSFUL RUNJOBS IN 4 RUNJOB STEPS RUN OR --> 60 % OF TOTAL RUNTASK STEPS RUN COMPLETED WITH A NON-ZERO RETURN CODE 3 NON-SUCCESSFUL SUBMITS IN 5 SUBMIT STEPS RUN OR --> 60 % OF TOTAL SUBMIT STEPS RUN COMPLETED WITH A NON-ZERO RETURN CODE
2-6
You can specify the start date and time and the stop date and time. The following table contains a description of the report fields.
Report Field NODE USERID PROC # PROC NAME STEP NAME **function type** Description Connect:Direct node where the statistics file is being examined. Connect:Direct userid. Connect:Direct Process number. Connect:Direct Process name. Name (or label) assigned to the Process step. Connect:Direct activity. Valid Process steps are PDS COPY, NONPDS COPY, RUN JOB, RUN TASK, and SUBMIT (within a Process). Data Process step began executing. Connect:Direct primary node. Connect:Direct secondary node. Connect:Direct completion code in hexadecimal format. Connect:Direct message ID. (COPY) Sending Connect:Direct node location name. (COPY) Source data set name. (COPY) Receiving Connect:Direct node location name. (COPY) Destination data set name. (RUNJOB) Data set containing job. (RUNJOB) Intended node location where the job is submitted.
mm/dd/yyyy PNODE SNODE COMPLETION CODE MSG ID SENDING NODE SRC DSNAME RECEIVING NODE DEST DSNAME DATASET CONTAINING JOB INTENDED NODE FOR JOB SUBMISSION PROGRAM NAME INTENDED NODE FOR PROGRAM EXECUTION DATASET CONTAINING PROCESS INTENDED NODE FOR PROCESS SUBMISSION message NON-SUCCESSFUL STEPS PROCESS STEPS RUN % TOTAL PROCESS STEPS WITH NON-ZERO CODE NON-SUCCESSFUL COPIES COPY STEPS RUN % TOTAL RUN JOB STEPS WITH NON-ZERO CODE
(RUNTASK) Program name. (RUNTASK) Intended attach node where the program is run.
(SUBMIT) Data set containing Process.
(SUBMIT) Intended node location where the Process is submitted.
Error message for Connect:Direct message ID. Total number of unsuccessful Process steps. Total number of Process steps run. Percentage of Process steps unsuccessful.
Number of unsuccessful COPY steps. Total number of COPY steps run. Percentage of RUN JOB steps unsuccessful.
2-7
Report Field NON-SUCCESSFUL RUNTASKS RUNTASK STEPS RUN % TOTAL RUNTASK STEPS WITH NON-ZERO CODE NON-SUCCESSFUL SUBMITS SUBMIT STEPS RUN % TOTAL SUBMIT STEPS WITH NON-ZERO CODE
Description Number of unsuccessful RUN TASK steps. Total number of RUN TASK steps run. Percentage of RUN TASK steps unsuccessful.
Number of unsuccessful SUBMIT (within a Process) steps. Total number of SUBMIT (within a Process) steps run. Percentage of SUBMIT (within a Process) steps unsuccessful.
Connect:Direct Security Violations Report

The Connect:Direct Security Violations Report lists the following types of violations for a specified time period:
! !
Signon security failures This failure is caused by an invalid userid or password that signed to Connect:Direct. Each violation is recorded. Process security failures This failure is caused when a Process does not run due to an invalid security authorization. An example is a Process that does not run because the user is not defined in the Connect:Direct authorization file at the remote node. Data set access security failures This failure is due to insufficient authority to access a data set.
A sample report follows.

CD SECURITY VIOLATIONS REPORT NODE = CD.BOSTON USERID CC MSG ID JONES 00000008 RACF095I SMITH 00000008 RACF095I MILLER 00000008 SAFA005I BYRAN 00000008 RACF098I BYRAN 00000008 RACF098I BYRAN 00000008 RACF098I GEORGE 00000008 SAFB004I WARREN 00000008 SAFB004I (ARS00004) DATE 06/17/1998 06/17/1998 06/17/1998 06/17/1998 06/17/1998 06/17/1998 06/17/1998 06/17/1998 TIME 10:34.30.5 10:49.21.1 12:26.10.4 17:55.15.8 17:56.37.5 17:57.03.1 19:00.30.2 20:00.30.2 17:12 WEDNESDAY, JUNE 24, 1998 2 VIOLATION TYPE DATASET DATASET SIGNON SIGNON SIGNON SIGNON PROCESS PROCESS
You can specify the start date and time and the stop date and time. Included in these reports are security message IDs generated by any security subsystem used with Connect:Direct. Security subsystems supported include:
! !
IBM Resource Access Control Facility (RACF) CA-ACF2 and CA-TOP SECRET by Computer Associates, Inc.

Report Field NODE USERID CC Description Connect:Direct node where the statistics file is being examined. Connect:Direct userid that created security violation. Connect:Direct completion code in hexadecimal format.
2-8
Report Field MSG ID DATE TIME VIOLATION TYPE
Description Security system message ID: Connect:Direct, ACF2, RACF, or TOP SECRET. Date security violation occurred. Time security violation occurred. Type of security violation. Valid types are SIGNON, PROCESS, and DATASET.
Connect:Direct Function Reports

The Connect:Direct Function Reports provide detailed information about specific Process steps for a specified time period. The following reports are included:
! ! ! ! !
Connect:Direct NonPDS Copy Report Connect:Direct PDS Copy Report Connect:Direct Run Job Report Connect:Direct Run Task Report Connect:Direct Submit Within a Process Report
You can request the start date and time and the stop date and time when requesting one of the Connect:Direct Function Reports.
Connect:Direct NonPDS Copy Report

The Connect:Direct NonPDS Copy Report provides information about COPY steps involving these transfers:
! ! !
NonPDS data set <--------> NonPDS data set NonPDS data set <--------> PDS data set member PDS data set member <--------> NonPDS data set
2-9
Following is an example of the Connect:Direct NonPDS Copy Report.

17:12 WEDNESDAY, JUNE 24, 1998 1 CD NON-PDS COPY REPORT (ARS00005) NODE = CD.BOSTON USERID PROC # PROC NAME STEP NAME TRANSMISSION INFORMATION ****** ****** ********* ********* *********************************************************** JONES 511 COPY05 COPY01 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY TRANSMISSION TIME = 0:00:06.96 COMPLETION CODE = 00000000 MSG 10 = SCPA000I COPY STEP SUCCESSFUL ==================================================== SRC DSNAME IS USERHLQ.OLDFILE1 DEST DSNAME IS USERHLQ.NEWFILE1 SENDING NODE ==> CD.BOSTON RECEIVING NODE ==> CD.JERSEY BYTES READ ==> 37200 BYTES WRITTEN ==> 37200 BLOCKS READ ==> 12 BLOCKS WRITTEN ==> 12 RECS READ ==> 0 RECS WRITTEN ==> 0 BYTES READ ==> 37224 BYTES RECEIVED ==> 37224 COMPRESSION% ==> -0.1 COMPRESSION% ==> -0.1 VOLSER ==> ABC003 VOLSER ==> PRD729 ---------------------------------------------------------------------------------------------------------------------MILLER 523 COPY07 COPY01 06/17/1998 PNODE = CD.BOSTON SNODE = CD.MIAMI TRANSMISSION TIME = 0:00:02.17 COMPLETION CODE = 00000000 MSG 10 = SCPA000I COPY STEP SUCCESSFUL ==================================================== SRC DSNAME IS USERHLQ.SAMPFILE(MEMBER) DEST DSNAME IS USERHLQ.COMPFILE SENDING NODE ==> CD.BOSTON RECEIVING NODE ==> CD.MIAMI BYTES READ ==> 1120 BYTES WRITTEN ==> 1120 BLOCKS READ ==> 1 BLOCKS WRITTEN ==> 1 RECS READ ==> 0 RECS WRITTEN ==> 0 BYTES READ ==> 1120 BYTES RECEIVED ==> 1120 COMPRESSION% ==> -0.2 COMPRESSION% ==> -0.2 VOLSER ==> DCM011 VOLSER ==> PRD011 ----------------------------------------------------------------------------------------------------------------------MILLER 523 COPY07 COPY01 06/17/1998 PNODE = CD.BOSTON SNODE = CD.MIAMI TRANSMISSION TIME = 0:00:00.87 COMPLETION CODE = 00000000 MSG 10 = SCPA000I COPY STEP SUCCESSFUL ==================================================== SRC DSNAME IS USERHLQ.FILE01 DEST DSNAME IS USERHLQ.FILE02 SENDING NODE ==> CD.BOSTON RECEIVING NODE ==> CD.MIAMI BYTES READ ==> 320 BYTES WRITTEN ==> 320 BLOCKS READ ==> 1 BLOCKS WRITTEN ==> 1 RECS READ ==> 0 RECS WRITTEN ==> 0 BYTES READ ==> 320 BYTES RECEIVED ==> 320 COMPRESSION% ==> -0.6 COMPRESSION% ==> -0.6 VOLSER ==> PRD011 VOLSER ==> DCM011 ----------------------------------------------------------------------------------------------------------------------
This report includes all NonPDS COPY step transmissions for a specified time period. The ARS software sorts COPY information for each SNODE by userid and then in ascending order by Process number. The following table contains a description of the report fields.
Report Field NODE USERID PROC # PROC NAME STEP NAME mm/dd/yyyy PNODE SNODE TRANSMISSION TIME Descriptions Connect:Direct node where the statistics file is being examined Connect:Direct userid Connect:Direct Process number Connect:Direct Process name Name (or label) assigned to a COPY step Date COPY step began executing Connect:Direct primary node Connect:Direct secondary node Elapsed time between when the COPY step started and when the COPY step completed Connect:Direct completion code in hexadecimal format Connect:Direct message ID Short message for Connect:Direct message ID
COMPLETION CODE MSG ID message
2-10
Report Field SRC DSNAME DEST DSNAME REPORT FIELD SENDING NODE RECEIVING NODE BYTES READ BYTES WRITTEN BLOCKS READ BLOCKS WRITTEN RECS READ RECS WRITTEN BYTES SENT BYTES RECEIVED COMPRESSION% COMPRESSION% VOLSER VOLSER
Descriptions Source data set name Destination data set name Description of report Name of node sending the data set Name of node receiving the data set Number of bytes read by sending node Number of bytes written by receiving node Number of blocks read by sending node Number of blocks written by receiving node (either blocks or records is displayed) Number of records read by sending node Number of records written by receiving node Number of bytes sent by sending node Number of bytes received by receiving node Compression percentage for sending data set Compression percentage for receiving data set Sending volume serial number Receiving volume serial number
Connect:Direct PDS Copy Report

The Connect:Direct PDS Copy Report provides information for each COPY step involving the following type of transfer:
!
PDS data set <--------> PDS data set
2-11
Following is an example of the Connect:Direct PDS Copy Report.

17:12 WEDNESDAY, JUNE 24, 1998 CD PDS COPY REPORT (ARS00006) NODE = CD.BOSTON STEP NAME TRANSMISSION INFORMATION ********* *************************** COPY01 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 00000000 MSGID = SCPAOOOI 1
USERID PROC # PROC NAME ****** ****** ********* JONES 420 PDSCOPY TRANSMISSION TIME = 0:00:05.42 COPY STEP SUCCESSFUL ================================================== SRC DSNAME IS USERHLQ.TESTPDS DEST DSNAME IS USERHLQ.NEWPDS SENDING NODE ==> CD.BOSTON RECEIVING NODE ==> CD.JERSEY BYTES READ ==> 22240 BYTES WRITTEN ==> 22240 BLOCKS READ ==> 11 BLOCKS WRITTEN ==> 11 RECS READ ==> 0 RECS WRITTEN ==> 0 BYTES SENT ==> 22262 BYTES RECEIVED ==> 22262 COMPRESSION% ==> -0.1 COMPRESSION% ==> -0.1 VOLSER ==> ABC003 VOLSER ==> ABC013 ABC005 ABC007 ABC009 ABC011 ============================================= MEMBER LIST ============================================= MEMBER 1 TO MEMBER 1 MEMBER 2 TO MEMBER 2 MEMBER 3 TO MEMBER 3 MEMBER 4 TO MEMBER 4 MEMBER 5 TO MEMBER 5 MEMBER 6 TO MEMBER 6 MEMBER 7 TO MEMBER 7 MEMBER 8 TO MEMBER 8 MEMBER 9 TO MEMBER 9 MEMBER 10 TO MEMBER 10 MEMBER 11 TO MEMBER 11 MEMBER 12 TO MEMBER 12
This report lists all PDS COPY step transmissions by Process number for a specified time period. It lists sending data set members names with each destination data set member name. We cannot guarantee the accuracy of the data in this report if you restart Connect:Direct using the TCQ=COLD initialization parameter during the time period specified. ARS uses the Process number in the statistics file to match PDS member names with a specific COPY step. Because a COLD restart begins numbering Processes from 1, ARS may not associate PDS member names correctly with the appropriate PDS Copy step. The following table shows a description of the report fields.
Report Field NODE USERID PROC # PROC NAME STEP NAME mm/dd/yyyy PNODE SNODE TRANSMISSION TIME Description Connect:Direct node where the statistics file is being examined Connect:Direct userid Connect:Direct Process number Connect:Direct Process name Name (or label) assigned to a COPY step Date COPY step began executing Name of primary node Name of secondary node Elapsed time between when the COPY step started and when the COPY step completed Connect:Direct completion code in hexadecimal format Connect:Direct message ID Short message for Connect:Direct message ID
COMPLETION CODE MSG ID message
2-12
Report Field SRC DSNAME DEST DSNAME SENDING NODE REPORT FIELD RECEIVING NODE BYTES READ BYTES WRITTEN BLOCKS READ BLOCKS WRITTEN RECS READ RECS WRITTEN BYTES SENT BYTES RECEIVED COMPRESSION% COMPRESSION% VOLSER VOLSER MEMBER LIST
Description Source data set name Destination data set name Name of node sending the data set Description of report Name of node receiving the data set Number of bytes read by sending node Number of bytes written by receiving node Number of blocks read by sending node Number of blocks written by receiving node (either blocks or records is displayed) Number of records read by sending node Number of records written by receiving node Number of bytes sent by sending node Number of bytes received by receiving node Compression percentage for sending data set Compression percentage for receiving data set Sending volume serial number Receiving volume serial number List of sending member names and receiving member names.
2-13
Connect:Direct Run Job Report

The Connect:Direct Run Job Report lists the jobs that are submitted to the system for execution using the Connect:Direct RUN JOB statement. Jobs are listed for a specified time period. Following is an example of the Connect:Direct Run Job Report.
17:12 WEDNESDAY, JUNE 24, 1998 CD RUNJOB REPORT (ARS00007) NODE = CD.BOSTON USERID PROC # PROC NAME STEP NAME RUNJOB INFORMATION ****** ****** ********* ********* *************************** JONES 414 ACCTJOB STEP1 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 00000000 MSG ID = SRJA000I CD-OS/390 RUN JOB FUNCTION COMPLETED SUCCESSFULLY ================================================== DSNAME ==> USERHLQ.CNTL(MEMBER4) JOB # ==> 1576 JOB SUBMITTED ON CD.BOSTON -----------------------------------------------------------------------------------MILLER 422 PAYJOB STEP00 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 80013000 MSG ID = SVSG010I NON-VSAM OPEN ERROR OCCURRED ================================================== DSNAME ==> USERHLQ.CNTL(MEMBER6) JOB # ==> 1576 INTENDED NODE FOR JOB SUBMISSION IS CD.BOSTON -----------------------------------------------------------------------------------SMITH 427 STATUS STEP03 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 80013000 MSG ID = SVSG010I NON-VSAM OPEN ERROR OCCURRED ================================================== DSNAME ==> USERHLQ.CNTL(NOTHE) JOB # ==> 1576 INTENDED NODE FOR JOB SUBMISSION IS CD.BOSTON -----------------------------------------------------------------------------------SMITH 428 UPDATE STEP01 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 00000000 MSG ID = SRJA000I CD-OS/390 RUN JOB FUNCTION COMPLETED SUCCESSFULLY ================================================== DSNAME ==> USERHLQ.CNTL(PRINT) JOB # ==> 6713 JOB SUBMITTED ON CD.BOSTON -----------------------------------------------------------------------------------1
The ARS software sorts all RUN JOB steps for each SNODE by userid and then in ascending order by Process number. The following table contains a description of the report fields.
Report Field NODE USERID PROC # PROC NAME STEP NAME mm/dd/yyyy PNODE REPORT FIELD SNODE COMPLETION CODE MSG ID message DSNAME Description Connect:Direct node where the statistics file is being examined Connect:Direct userid Connect:Direct Process number Connect:Direct Process name Name (or label) assigned to a RUN JOB step Date RUN JOB step submitted to run Connect:Direct primary node Description of report Connect:Direct secondary node Connect:Direct completion code in hexadecimal format Connect:Direct message ID Short message for Connect:Direct message ID Data set name containing job stream to be submitted
2-14
Report Field JOB # JOB SUBMITTED ON
Description Number assigned to job by operating system Connect:Direct node where the job is submitted to run
Connect:Direct Run Task Report

The Connect:Direct Run Task Report tracks all tasks (programs) for a specified time period that executed under the control of the Connect:Direct RUN TASK statement. Following is an example of the Connect:Direct Run Task Report.
17:12 WEDNESDAY, JUNE 24, 1998 CD RUNJOB REPORT (ARS00008) NODE = CD.BOSTON USERID PROC # PROC NAME STEP NAME RUNTASK INFORMATION ****** ****** ********* ********* *************************** JONES 424 PAYROLL STEP1 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 80806000 MSG ID = SRTA004I CD-OS/390 RUN TASK CANNOT FIND SPECIFIED TASK IN STEP LIBRARY ================================================== PROGRAM NAME ==> IDONTNO INTENDED NODE FOR PROGRAM ATTACHMENT IS CD.BOSTON -----------------------------------------------------------------------------------JONES 415 PAYJOB STEP1 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 00000000 MSG ID = SRTA000I CD-OS/390 RUN TASK FUNCTION SUCCESSFULLY COMPLETED ================================================== PROGRAM NAME ==> IEFBR14 PROGRAM ATTACHED ON CD.BOSTON -----------------------------------------------------------------------------------MILLER 425 RUNT STEP1 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 80806000 MSG ID = SRTA004I CD-OS/390 RUN TASK CANNOT FIND SPECIFIED TASK IN STEP LIBRARY ================================================== PROGRAM NAME ==> IDONTNO INTENDED NODE FOR PROGRAM ATTACHMENT IS CD.BOSTON -----------------------------------------------------------------------------------SMITH 430 RUNT STEP1 06/17/1998 PNODE = CD.BOSTON SNODE = CD.JERSEY COMPLETION CODE = 00000000 MSG ID = SRTA000I CD-OS/390 RUN TASK FUNCTION SUCCESSFULLY COMPLETED ================================================== PROGRAM NAME ==> IEFBR14 PROGRAM ATTACHED ON CD.BOSTON 1
The ARS software sorts all RUN TASK steps for each SNODE by userid and then in ascending order by Process number. The following table contains a description of the report fields.
Report Field NODE USERID PROC # PROC NAME STEP NAME mm/dd/yyyy PNODE REPORT FIELD SNODE COMPLETION CODE Description Connect:Direct node where the statistics file is being examined Connect:Direct userid Connect:Direct Process number Connect:Direct Process name Name (or label) assigned to a RUN TASK step Date RUN TASK step attached and executed Connect:Direct primary node Description of report Connect:Direct secondary node Connect:Direct completion code in hexadecimal format
2-15
Report Field MSG ID message PROGRAM NAME PROGRAM ATTACHED ON
Description Connect:Direct message ID Short message for Connect:Direct message ID Name of program module attached Connect:Direct node where the task is attached and executed
Connect:Direct Submit Within a Process Report

The Connect:Direct Submit Within a Process Report lists Processes that are submitted to Connect:Direct for execution using the Connect:Direct Submit (within a Process) statement for a specified time period. Following is an example of the Connect:Direct Submit Within a Process Report.
17:12 WEDNESDAY, JUNE 24, 1998 CD SUBMIT WITHIN A PROCESS REPORT (ARS00009) NODE = CD.BOSTON USERID PROC # PROC NAME STEP NAME SUBMIT INFORMATION ****** ****** ********* ********* *************************** LISA 418 SUB SUBSTEP 06/17/1998 PNODE = CD.BOSTON SNODE =CD.JERSEY COMPLETION CODE = 80000000 MSG ID = SSUB000I THE SUBMIT CONTROL BLOCK HAS BEEN SUCCESSFULLY CONSTRUCTED ================================================== PROGRAM NAME ==> TESTHLQ.CD.DEVTEST PROC(LISA01) PROCESS SUBMITTED ON CD.BOSTON -----------------------------------------------------------------------------------LISA 426 SUB SUBSTEP 06/17/1998 PNODE = CD.BOSTON SNODE =CD.JERSEY COMPLETION CODE = 00000008 MSG ID = SSUB005I UNABLE TO ALLOCATE DSN SPECIFIED IN SUBMIT STATEMENT ================================================== DSNAME ==> THERE IS NO SUCH LIBRARY AS THIS(NOEXIST) INTENDED NODE FOR PROCESS SUBMISSION IS CD.BOSTON -----------------------------------------------------------------------------------LISA 431 SUB SUBSTEP 06/17/1998 PNODE = CD.BOSTON SNODE =CD.JERSEY COMPLETION CODE = 00000004 MSG ID = SBPA016I DATA SET MEMBER NOT FOUND ================================================== DSNAME ==> TESTHLQ.CD.DEVTEST PROC(NOMEMB) INTENDED NODE FOR PROCESS SUBMISSION IS CD.BOSTON -----------------------------------------------------------------------------------LISA 432 SUB SUBSTEP 06/17/1998 PNODE = CD.BOSTON SNODE =CD.JERSEY COMPLETION CODE = 00000008 MSG ID = SPQG002I SPECIFIED SNODE NOT AVAILABLE ================================================== DSNAME ==> TESTHLQ.CD.DEVTEST PROC(NAME01) INTENDED NODE FOR PROCESS SUBMISSION IS CD.BOSTON -----------------------------------------------------------------------------------LISA 433 SUB SUBSTEP 06/17/1998 PNODE = CD.BOSTON SNODE =CD.JERSEY COMPLETION CODE = 00000008 MSG ID = SSUB002I THE SUBMIT CONTROL BLOCK HAS BEEN SUCCESSFULLY CONSTRUCTED ================================================== DSNAME ==> TESTHLQ.CD.DEVTEST PROC(NAME01) PROCESS SUBMITTED ON CD.BOSTON 1
The ARS software sorts all SUBMIT steps for each SNODE by userid and then in ascending order by Process number. The following table contains a description of the report fields.
Report Field NODE USERID PROC # PROC NAME STEP NAME mm/dd/yyyy Description Connect:Direct node where the statistics file is being examined Connect:Direct userid Connect:Direct Process number Connect:Direct Process name Name (or label) assigned to a SUBMIT (within a Process) step Date SUBMIT (within a Process) step ran
2-16
Report Field PNODE REPORT FIELD SNODE COMPLETION CODE MSG ID message DSNAME
Description Connect:Direct primary node Description of report Connect:Direct secondary node Connect:Direct completion code in hexadecimal format Connect:Direct message ID Short message for Connect:Direct message ID Data set name containing the Connect:Direct Process. Only available when SUBNODE=PNODE. Connect:Direct node where the Process was submitted to run
PROCESS SUBMITTED ON
Chapter 3
Requesting ARS Reports Using Screens
This chapter explains how to request ARS statistical reports using ARS screens. Request these reports by completing the following two steps:
! !
Step 1Request the ARS report using ARS screens Step 2Run the job
ARS screens build a job stream to produce any of the ARS reports. For this reason, the screens are most useful in cases where you need individual reports instead of volume reports. After ARS screens build the job stream and submit it to run, the job performs the following:
! ! ! ! ! !
Signs on to Connect:Direct Creates a temporary data set to hold the specified statistics Accesses the Connect:Direct statistics file and copies statistics to a temporary data set Executes the requested ARS report routine using the Connect:Direct statistics as input data Sends the report to the selected output location Deletes the temporary data set Note: Connect:Direct must be active in order to use ARS.
Step 1Requesting Reports Using ARS Screens

The ARS screens prompt you to provide information that automatically builds the job discussed in Step 2 of this chapter. Certain information entered on these screens is retained between sessions to alleviate the need for entering identical information each time you request a report.
3-2
Accessing the ARS Screens Using the Connect:Direct Interactive Interface (IUI)
To access the ARS screens through the IUI, select the ADMIN option from the Primary Options Menu.
Connect:Direct PRIMARY OPTIONS MENU CMD ==> ADMIN SELECT CF SB DF SS CP DP FP SP PS ONE OF THE FOLLOWING: - COPY A FILE - SUBMIT A PREDEFINED PROCESS - DEFINE A PROCESS USING ISPF EDIT - VIEW STATISTICS FOR A COMPLETED PROCESS CHANGE CHARACTERISTICS OF A PROCESS DELETE A NON-EXECUTING PROCESS FLUSH AN EXECUTING PROCESS VIEW DATA ABOUT AN EXECUTING PROCESS SUSPEND AN EXECUTING PROCESS
******************* * * * TODAY:1998.06.24* * TIME: 09:20 * * * *******************
MSG SW SD NM WHO SPF AUTH MS ADMIN
VIEW Connect:Direct MESSAGE TEXT SWAP AMONG CONCURRENT Connect:Direct SESSIONS VIEW/CHANGE YOUR Connect:Direct SIGNON INFORMATION DEFAULTS VIEW INFORMATION IN THE Connect:Direct NETWORK MAP VIEW CHARACTERISTICS OF YOUR Connect:Direct IUI ENVIRONMENT ENTER ISPF/PDF - VIEW YOUR Connect:Direct FUNCTION AUTHORIZATION SIGN ON TO MULTIPLE Connect:DIRECT NODES CONCURRENTLY - PERFORM Connect:Direct ADMINISTRATIVE FUNCTIONS
From the Administrative Options Menu, select the ARS option.

Connect:Direct ADMINISTRATIVE OPTIONS MENU CMD ==> ARS SELECT ONE OF THE FOLLOWING: ST - VIEW TYPE RECORD IT - INSERT/UPDATE TYPE RECORD DT - DELETE TYPE RECORD SU IU DU TS TF MD C SN ARS NM UNM INQ STAT - VIEW USER AUTHORIZATION RECORD - INSERT/UPDATE USER AUTHORIZATION RECORD - DELETE USER AUTHORIZATION RECORD - VIEW Connect:Direct TASKS - FLUSH A Connect:Direct TASK MODIFY Connect:Direct TRACE CHARACTERISTICS ENTER A NATIVE Connect:Direct COMMAND TERMINATE Connect:Direct ARS REPORTING FACILITY VIEW THE CONTENTS OF THE Connect:Direct NETWORK MAP UPDATE THE Connect:Direct NETWORK MAP
******************* * * * TODAY:1998.06.24* * TIME: 09:23 * * * *******************
- INQUIRE ABOUT DTF INTERNAL STATUS - PERFORM STATISTICS FUNCTIONS
Chapter 3 / Requesting ARS Reports Using Screens
3-3
Accessing the ARS Screens

In addition to the IUI, you can access the ARS screens by using one of following methods:
! !
Request the ARS option defined on the ISPF Primary Option Menu Request the TSO COMMAND Option (Option 6) from the ISPF Primary Option Menu and type the following.
ARS
Type the following at the command line on any ISPF screen.

==> TSO %ARS
The following table contains a description of these ARS signon parameters.

Parameters TSO ARS Description of ARS Signon Parameters (optional) specifies a TSO command. Use it when accessing ARS from the ISPF command line. specifies the name of the CLIST that accesses the ARS screens.
ARS Report Options Screen

The ARS Report Options Screen in the following figure enables you to request the report, provide signon data, and specify the time period covered in the report. If you already requested ARS reports using these screens and do not need to change any other data, you can bypass the remaining screens by typing SUB (submit) at the CMD field, then pressing Enter. This command automatically submits the job stream to run.
$cd.node CMD ==> AC SM EX SC -
Connect:Direct OS/390 - ARS REPORT OPTIONS hh:mm ACTIVITY SUMMARY EXCEPTION SECURITY ==> EDIT JCL ==> (Y,N) PS PO RJ RT SB NON-PDS COPY PDS COPY RUNJOB RUNTASK SUBMIT
REPORT TYPE
Connect:Direct SIGNON PARAMETERS -------------------------------USER ID ==> $uid PASSWORD ==> NETMAP NAME ==> $cd.netmap TRANSPORT ==> NET COMMUNICATION ADDRESS ==> ( , REPORTING RANGE --------------START DATE ==> STOP DATE ==>
START TIME STOP TIME
==> ==>
3-4
The following table contains a description of the screen fields.

Field REPORT TYPE EDIT JCL USER ID Description Specifies the ARS report. Specifies an option to edit JCL. Specifies the userid for signing on to Connect:Direct, if your security environment requires it. (optional) Specifies the password needed to access Connect:Direct. (optional) Specifies the name of the Connect:Direct Network Map. Enables override of signon defaults for DMBATCH transport type. Specifies port number and IP address with TRANSPORT=TCP.
PASSWORD NETMAP NAME TRANSPORT COMMUNICATIONS ADDRESS REPORTING RANGE
Identifies the date, day or time period that you want the requested report to cover. (optional) If all four fields are blank, the entire contents of the Connect:Direct statistics file is used. Specifies the date or day that the statistics records are selected for the ARS report. You can specify the day (dd), month (mm), and year (yy for 2-digit year and yyyy for 4-digit year). Use periods or backslashes (\) to separate the components of a date value. You can specify the date (dd), month (mm), and year (yy) in one of the following formats: yymmdd or yyyymmdd; yy/mm/dd or yyyy/mm/dd; yy.mm.dd or yyyy.mm.dd; mmddyy or mmddyyyy; mm/dd/yy or mm/dd/yyyy; mm.dd.yy or mm.dd.yyyy; or the Julian date, yyddd or yyyyddd; yy/ddd or yyyy/ddd; or yy.ddd or yyyy.ddd. If you only specify the date, the time defaults to 00:00. This date must have the same format as specified in the DATEFORM initialization parameter. You can also use day in these fields to indicate day of the week for which the statistics records are searched. Valid names include MOnday, TUesday, WEdnesday, THursday, FRiday, SAturday, and SUnday. You can also specify TODAY, which searches for the statistics records today; or TOMORROW, which searches for statistics records the next day; or YESTER, which searches for statistics records for yesterday. Specifies the time of day in hours (hh), minutes (mm), and seconds (ss) when the statistics records are selected for the ARS report. Specify AM or PM. You can express the time of day using the 24-hour clock or the 12-hour clock. If you use the 24-hour clock, valid times are 00:00-24:00. If you use the 12-hour clock, you can express 1:00 hours as 1:00AM, and you can express 1:00 PM as 13:00 hours. If you do not use AM and PM, the 24-hour clock is assumed. You do not need to specify minutes and seconds. You can also specify NOON, which searches for the statistics records at noon, or MIDNIGHT, which searches for the statistics records at midnight. The default for the time is 00:00:00, the beginning of the day. If you do not specify START TIME and STOP TIME but you do specify the START DATE and STOP DATE, the time range default is 00:00 to 24:00.
START DATE or STOP DATE
START TIME or STOP TIME
3-5
ARS Connect:Direct Requirements Screen

The ARS Connect:Direct Requirements screen in the following figure identifies specific job stream parameters for the job card and Connect:Direct-related information.
$cd.node CMD ==>
Connect:Direct OS/390 - ARS (Job and File Requirements) hh:mm
UP TO 3 LINES FOR JOBCARD INFO ==> ________________________________________________________________________ ==> ________________________________________________________________________ ==> ________________________________________________________________________ STEPLIB DATA SET NAME FOR Connect:Direct PROGRAMS (OPTIONAL): ==> ____________________________________________ ==> ____________________________________________ Connect:Direct PUBLIB PROCESS LIBRARIES (1 REQUIRED): ==> ____________________________________________ ==> ____________________________________________ Connect:Direct MESSAGE DATA SET NAME (REQUIRED): ==> ____________________________________________ UNIT SPECIFICATION FOR Connect:Direct TEMPORARY DATASET: ==> ________

Field JOBCARD INFO Description Specifies typical job card information. Use the COND=(0,NE) for best results. This means that Step 2 of the job does not run if an error is found in Step 1. Specifies the name of the library containing the Connect:Direct load modules. You can type two libraries in this section (optional). Specifies the name of the library containing Connect:Direct Processes.
STEPLIB DATA SET NAME FOR Connect:Direct PROGRAMS Connect:Direct PUBLIC PROCESS LIBRARIES Connect:Direct MESSAGE DATA SET NAME
Specifies the name of the message data set containing the Connect:Direct messages.
3-6
ARS SAS Requirements Screen

The ARS SAS Requirements screen in the following figure identifies specific JCL parameters for SAS-related information.
$cd.node CMD ==>
Connect:Direct OS/390 - ARS (SAS Files and Output) hh:mm
SAS CATALOGED PROCEDURE (REQUIRED): ==> ____________________________________________ DATASET NAME CONTAINING SAS ROUTINES (REQUIRED): ==> ____________________________________________ ONE OF THE FOLLOWING MUST BE PROVIDED : OUTPUT DATA SET NAME : ==> ____________________________________________ OUTPUT (SYSOUT) CLASS : ==> _

Field SAS CATALOGED PROCEDURE DATA SET NAME CONTAINING SAS ROUTINES OUTPUT DATA SET NAME Description Identifies the name of the SAS cataloged procedure, which is a collection of JCL statements required to execute SAS for batch processing at your installation. Specifies where the ARS routines ($CD.MAPLIB) that interact with SAS are located.
You must preallocate the sequential data set designated in this field with the following attributes: RECFM=FBA LRECL=240 BLKSIZE=3120 If this field is left blank, you must specify the OUTPUT (SYSOUT) CLASS field.
OUTPUT (SYSOUT) CLASS
Specifies the SYSOUT class that automatically sends the output to a designated printer queue (optional). If you leave this field blank, you must specify the OUTPUT DATASET NAME field. Note: If you are requesting the Connect:Direct Summary report and routing it to a data set, ensure that the data set is empty. If the data set is not empty, this report is placed after the data already in the data set. The Connect:Direct Summary Report is automatically allocated with DISP=MOD instead of DISP=SHR.
3-7
Displayed Job Stream Created from Screens

After completing the ARS screens, ARS builds a job stream, as in the following example, based on what you entered on the screens. If you requested EDIT, ARS displays the job after completing the screens. You can review the job stream before submitting it. Following is an example of the JCL which is generated using member CDARS from $CD.ISPSLIB.
//JOBNAME JOB (ACCT), NAME, NOTIFY=TSOID,TIME=((1), //REGION=1024K,MSGCLASS=X,CLASS=B //* //* //DMBATCH EXEC PGM=DMBATCH,PARM=YYSLN //STEPLIB DD DISP=SHR,DSN=$CD.LINKLIB //SYSUDUMP DD SYSOUT=* //DMPUBLIB DD DISP=SHR,DSN=$CD.PROCESS //DMMSGFIL DISP=SHR,DSN=$CD.MSG //TEMPDSN DSN=&CDAPI,DISP=(NEW,PASS),UNIT=PTEMP, // DCB=(DSORG=PS,RECFM=VBA,LRECL=4100,BLKSIZE=4104), // SPACE=(4104,(70,13)) //DMPRINT DD SYSOUT=* //SYSIN DD * SIGNON USERID=(NAME,,) NETMAP=$CD.NETMAP TMPDD=TEMPDSN SEL STAT WHERE (STARTT = (06/1/1998,12:00AM) STOPT = 07/1/1998,11:59PM) ) FILE SIGNOFF /* //* ///SASTEP EXEC $SASPROC, // OPTIONS=DQUOTE MACRO MACROGEN MERROR MISSING="-" //WORK DD UNIT=PTEMP,SPACE=(CYL,(20,10)) //NDMX0001 DD DISP=(OLD,DELETE),DSN=&CDAPI //DMMSGFIL DD DISP=SHR,DSN=$CD.MSG //FT20F001 DD DISP=SHR,DSN=$OUTPUT.DATASET.NAME //SYSIN DD DISP=SHR,DSN=$CD.MAPLIB(ACTIVITY)
Step 2Running the Job

If you type COND=(0,NE) in the JOBCARD INFO field of the requirements screen, ARS bypasses Step 2 if Step 1 does not complete successfully. When the job runs, it performs the following:
! ! ! ! ! !
Signs on to Connect:Direct Creates a temporary data set to hold the specified statistics Accesses the Connect:Direct statistics file and copies statistics to the temporary data set Executes the requested ARS report routine using the Connect:Direct statistics as input data Sends the report to the selected output location Deletes the temporary data set
3-8
Chapter 4
Requesting Multiple ARS Reports or Scheduled Processing
This chapter explains how to request ARS reports without using the ARS screens. You can:
! !
Submit multiple ARS reports at one time Submit ARS reports for scheduled processing
You can request ARS reports without using ARS screens by editing a sample job stream to specify processing requirements and report types. Also, when the output of a multiple report request is routed to a data set, some ARS report routines can require a minor edit change. This chapter contains the following:
! ! !
Sample job stream with instructions for modifying it, and definitions of the parameters and SAS options used in the job stream Instructions for editing the sample Connect:Direct OS/390 Process that enables you to schedule the report requested Instructions for editing ARS report routines when multiple reports are routed to an output data set
4-2
Sample Job Stream

The purpose of this section is to:
! !
Explain how to modify the sample job stream Define the parameters used in the job stream
The sample job stream is located in the data set named $CD.CNTL(ARSJCL).
Modifying the Sample Job Stream

The following figure is a sample job stream. This job stream requests all of the ARS reports in one step. Make the following modifications of the sample job stream: 1. 2. 3. 4. 5. 6. 7. 8. 9. Modify the job card with the appropriate information. Change $CD.LINKLIB to the appropriate Connect:Direct load library name. Change $CD.PROCESS to the appropriate Connect:Direct Process library name. Change all occurrences of $CD.MSG to the Connect:Direct message data set name. Change $UID to your Connect:Direct user ID. Also add the password, if needed. Change $CD.NETMAP to your Network Map data set name. Change all occurrences of $UNITNAME to the valid unit name. Change $SASPROC to the name of the SAS cataloged procedure used at your installation. Route the output to one of the two options:
! !
Route to the SYSOUT class. Change all occurrences of $OUTPUT.DATASET.NAME to the name of the data set to which you route the output. Preallocate this data set as FBA with an LRECL of 240 and BLKSIZE of 3120. Ensure that the data set is empty before running this job. Complete the instructions in Routing Multiple Reports to an Output Data Set on page 4-5. Note: This option is commented out in the sample job.
10. Change $CD.MAPLIB to the name of the data set containing the SAS programs.
Chapter 4 / Requesting Multiple ARS Reports or Scheduled Processing
4-3
Following is an example of the ARSJCL member found in $CD.CNTL.
//JOBNAMEX JOB (ACTNG), PRGRMR, NOTIFY=TSOID,TIME=((1),COND=(0,NE), // REGION=1024k,MSGCLASS=,CLASS=, //****************************************************************************/ //* THIS JCL CAN BE EDITED TO CREATE A JOB STREAM THAT RUNS */ //* ARS INDEPENDENTLY OF THE ARS PANELS. IT IS SET UP TO */ //* PRODUCE MULTIPLE REPORTS. FOLLOW THE INSTRUCTIONS OUTLINED BELOW. */ //* */ //* */ //* 1) MODIFY JOB CARD WITH APPROPRIATE INFORMATION. */ //* 2) CHANGE $CD.LINKLIB TO BE THE NAME OF THE C:D LOAD LIBRARY. */ //* 3) CHANGE $CD.PROCESS TO BE THE NAME OF THE C:D PROCESS LIBRARY. */ //* 4) CHANGE ALL OCCURRENCES OF $CD.MSG TO THE NAME OF THE C:D */ //* MESSAGE DATA SET. */ //* 5) CHANGE $UID IN SIGNON CMD TO YOUR C:D USERID-ADD PSWD IF NEC. */ //* 6) CHANGE $CD.NETMAP TO YOUR NETWORK MAP DATA SET NAME. */ //* 7) CHANGE ALL OCCURRENCES OF $UNITNAME TO VALID UNIT. */ //* 8) CHANGE $SASPROC TO THE NAME OF SAS CATALOGED PROCEDURE USED AT */ //* YOUR INSTALLATION. */ //* 9) ROUTE OUTPUT TO A SYSOUT CLASS (LOOK FOR FT20F001 DD) */ //* */ //* OR ... */ //* */ //* 9) CHANGE ALL $OUTPUT.DATASET.NAME TO THE NAME OF THE DATA SET YOU */ //* HAVE CHOSEN TO ROUTE THE OUTPUT TO. THIS DATA SET SHOULD BE */ //* ALLOCATED AS FBA WITH AN LRECL OF 240 AND BLKSIZE OF 3120. */ //* THIS DATA SET SHOULD BE EMPTY BEFORE RUNNING THIS JOB. */ //* (DO NOT FORGET TO DELETE THE ASTERISK ON THIS LINE IN THE JOB */ //* AND PLACE IT ON THE LINE ABOVE BEFORE RUNNING.) */ //* */ //* A) BECAUSE THE SAS PROGRAMS ARE SET UP TO BE RUN INDIVIDUALLY, */ //* YOU MUST EDIT THE MEMBERS ACTIVITY AND SECURITY IN */ //* YOUR $CD.MAPLIB DATA SET IN THE FOLLOWING MANNER: */ //* */ //* CHANGE THE SAS STATEMENT ... */ //* PROC PRINTTO NEW UNIT=20; TO ... */ //* */ //* PROC PRINTTO UNIT=20; */ //* */ //* THIS WILL CAUSE THE OUTPUT FROM EACH REPORT TO APPEND TO */ //* THE END OF THE OUTPUT FILE RATHER THAN OVERLAY WHATS */ //* ALREADY THERE. */ //* */ //* 10) CHANGE $CD.MAPLIB TO THE NAME OF THE DATA SET CONTAINING */ //* THE SAS PROGRAMS. */ //* */ //* NOTE - IF YOU WOULD LIKE TO PUT SPECIFIC BOUNDARIES ON THE TIME */ //* SPAN TO BE REPORTED ON, MODIFY THE SEL STATISTICS COMMAND IN */ //* THE SYSIN STREAM OF THE DMBATCH STEP TO CONTAIN START AND STOP */ //* TIMES. AS IS, REPORTING WILL OCCUR ON THE ENTIRE STAT FILE. */ //****************************************************************************/ //DMBATCH EXEC PGM=DMBATCH,PARM=YYSLN //STEPLIB DD DSN=$CD.LINKLIB,DISP=SHR //DMPUBLIB DD DSN=$CD.PROCESS,DISP=SHR //DMMSGFIL DD DSN=$CD.MSG,DISP=SHR //TEMPDSN DD DSN=&CDAPI,DISP=(NEW,PASS),DCB=(DSORG=PS, // RECFM=VBA,LRECL=4100,BLKSIZE=4104),SPACE=(4104,(70,13)), // UNIT=$UNITNAME //DMPRINT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSIN DD* SIGNON USERID=($UID) NETMAP=$CD.NETMAP TMPDD=TEMPDSN SEL STAT WHERE () FILE SIGNOFF /* //* ///SASTEP EXEC $SASPROC, // OPTIONS=DQUOTE MACRO MACROGEN MERROR MISSING="-" //WORK DD UNIT=$UNITNAME,SPACE=(CYL,(20,10)) //NDMX0001 DD DISP=(OLD,DELETE),DSN=&CDAPI //DMMSGFIL DD DISP=SHR,DSN=$CD.MSG //SASPROGS DD DISP=SHR,DSN=$CD.MAPLIB //FT20F001 DD SYSOUT=* //*FT20F001 DD DISP=MOD,DSN=$OUTPUT.DATASET.NAME //SYSIN DD * %INCLUDE SASPROGS(ACTIVITY,SUMMARY,EXCEPT,SECURITY,NPDSCOPY,PDSCOPY, RUNJOB,RUNTASK,SUBMIT); //*
Job Stream Definitions

The following table defines the parameters and SAS options for the sample job stream.
Report Field JOBCARD INFO Definition Specifies the typical job card information. Use the COND=(0,NE) for best results. This means that the second step of the job does not run if an error occurs in the first step. Specifies the program name of the Connect:Direct batch interface.
DMBATCH
4-4
Report Field STEPLIB DMPUBLIB DMMSGFIL TEMPDSN
Definition Specifies the library containing the Connect:Direct load modules. Specifies the library containing the Connect:Direct Processes. Specifies the Connect:Direct message data set that accesses the Connect:Direct messages. Specifies the temporary data set containing the extract from the Connect:Direct statistics file that is used as input to SAS. This is always specified as (NEW, PASS) so that when you create the data set, the extracted data is saved in it, and then passed on to the next step. Specifies where the job output from DMBATCH goes. This is useful if an error occurs in DMBATCH. Specifies where the job execution messages goes. Contains the Connect:Direct control statements to extract from the statistics file. You can represent SYSIN as a sequential data set, PDS member, or instream data set. Specifies the name of the SAS cataloged procedure used at your installation with the following options: DQUOTE specifies that the system accepts double quotes. MACRO specifies that the SAS macro library is available. MACROGEN specifies that the system can print SAS macros. MERROR specifies that a warning message is produced if a name is prefixed with a percent sign to indicate a SAS macro, but the name is not a valid SAS macro. MISSING specifies that dashes (-) are inserted when a numeric character is missing in the report field. Specifies the work area used by SAS for processing. Specifies the temporary data set that contains the extract from the Connect:Direct statistics file. Specify the data set parameters (OLD, DELETE) so that the data set is deleted automatically after processing. Specifies the name of the Connect:Direct message data set. Identifies the name of the data set containing the SAS routines to produce the reports. See %INCLUDE parameter in this table. Specifies the DD statement used by SAS to route output. This DD statement can be either output to a data set or SYSOUT class. If it is to a data set, you must preallocate the data set, it must be sequential, and have the following attributes: RECFM=FBA; LRECL=240; BLKSIZE=3120. Specifies SYSIN for SAS. Contains a special SAS control statement that enables you to execute SAS programs that are stored separately from their JCL. The first name after SASPROGS identifies the DD name that references the location of the SAS programs. The requested ARS report routine names are placed inside of the parentheses: ACTIVITY specifies the Connect:Direct Activity Report EXCEPT specifies the Connect:Direct PDS Copy Report RUNJOB specifies the Connect:Direct Run Job Report. RUNTASK specifies the Connect:Direct Run Task Report. SECURITY specifies the Connect:Direct Security Violations Report. SUBMIT specifies the Connect:Direct Submit Within a Process Report. SUMMARY specifies the Connect:Direct Summary Report.
DMPRINT (Optional)
SYSPRINT SYSIN
SASTEP
WORK NDMX0001
DMMSGFIL SASPROGS
FT20F001
SYSIN %INCLUDE
Chapter 4 / Requesting Multiple ARS Reports or Scheduled Processing
4-5
Sample Connect:Direct Process That Submits Job Stream

The RPTPROC member in $CD.SAMPLIB in the following figure contains a Connect:Direct Process that runs the job stream discussed in the previous section, Modifying the Sample Job Stream on page 4-2. You can set up the sample Process to run automatically on a specified time interval, by submitting this Process with the Connect:Direct SUBMIT command, specifying the STARTT parameter and RETAIN=YES parameter.
RPTPROC * THIS PROCESS WILL SUBMIT FOR EXECUTION THE JCL TO RUN ARS * CHANGE $SECONDARY.NODE TO THE DESIRED SNODE NAME FOR THE PROCESS * CHANGE $TSOID TO YOUR TSO ID * CHANGE $CD.CNTL(ARSJCL) TO THE DATA SET NAME CONTAINING THE JCL * TO RUN ARS PROCESS SNODE=$SECONDARY.NODE NOTIFY=$TSOID STEPONE RUN JOB ( DSN=$CD.CNTL(ARSJCL) )
You need to modify the following items if you choose to use this sample Process. 1. 2. 3. Change $SECONDARY.NODE to the appropriate SNODE. Change $TSOID to your TSO ID. Change $CD.CNTL(ARSJCL) to the data set name containing the job that runs ARS. (See STEPONE.)
For convenience, you may want to replace RPTPROC in your Connect:Direct Process library after editing it.
Routing Multiple Reports to an Output Data Set

Complete this step only when you request multiple ARS report types in one job and the reports are sent to an output data set. The Connect:Direct Activity Report and Connect:Direct Security Violations Report require a minor edit change in the ARS routine if you include them in a multiple report request. Before modifying the ARS routines, you may want to make a copy of the $CD.MAPLIB, which contains all of the report routines. Use the first copy when you request only one report (in batch mode or using the ARS screens). The second copy can contain the modified routines for use when you make multiple report requests in a job. You can report the ARS report routines using TSO. The routines are in the $CD.MAPLIB. The following table lists the types of reports and the corresponding members in the $CD.MAPLIB that require modification.
Report Type Connect:Direct Activity Report Connect:Direct Security Violations Report Member Name ACTIVITY SECURITY
4-6
Modify the PROC PRINTTO statement listed in the members so that the output from one report appends rather than overlaying output from the previous report in the designated output file. Change the ARS report routine from:
PROC PRINTTO NEW UNIT=20
to:
PROC PRINTTO UNIT=20;
Chapter 5
ARS Record Layouts
This chapter contains the information you need to customize ARS reports. You can either modify the ARS reports or you can develop new reports. Examples include the following:
! !
Change ARS report headings, spacing, field titles, and output format Access additional information from the Connect:Direct statistics file to enhance ARS reports or to develop new reports
The ARS routines do not utilize all of the Connect:Direct fields in the Connect:Direct statistics records. To assist you in customizing reports, this chapter lists all of the Connect:Direct fields. The SAS Informat variables for these records are located in the $CD.MAPLIB library. Access the information by the member names listed in the following table. Note: Use the two character designations for records types when you browse the Connect:Direct statistics file.
Member Name CDAER Contents of Member Authorization Event Record Record Types IU=INSert USER UU=UPDate USER SU=SELect USER DU=DELete USER CH=CHange PROCess CT=COPY DP=DELete PROCess SP=SELect PROCess DT=SELect TASK FT=FLUSH TASK SS=SELect STATistics SN=SELect NETmap FP=FLUSH PROCess MC=PDS member COPY PS=SUBmit statement SW=SUBmit command PT=PROCess RJ=RUN JOB
CDCPTR CDCTR CDDPTR CDDTR
Change Process Termination Record Copy Termination Record Delete Process Termination Record Display Statistics Record
CDFPTR CDFMCR CDPSSR
Flush Process Termination Record PDS Member Copy Record Process Submit Statistics Record
CDPTR CDRJTR
Process Termination Record Run Job Termination Record
5-2
Member Name CDRTTR CDSFR
Contents of Member Run Task Termination Record Signon/Signoff Statistics Record
Record Types RT=RUN TASK SI=SIGNON SO=SIGNOFF SD=Start Connect:Direct ST=STOP CD TS=Stop session WT=Write to Operator
CDSDCR CDSTDCR CDSTSR CDFWTOST
Start Connect:Direct Command Record Stop Connect:Direct Statistics Record Stop Session Statistics Record Write to Operator (WTO) Statistics Record
Description of an SAS Variable

The SAS Informat variables for these records are located in the $CD.MAPLIB library. An example of a SAS Informat variable is @5 SASFIELD PK1. Variable descriptions for this example are listed in the following table.
Variable @n Description Identifies the position of the variable in the Connect:Direct statistics record (relative to 1). Always identified by an @. Specifies the SAS name for the corresponding Connect:Direct field name. The SAS name variable must follow the position variable (@n). Specifies the type and length of the SAS Informat variable used in the maps. The type variable must follow the name variable (SASFIELD). Type variable used in the maps are: HEX - numeric hexadecimal IB - integer binary PD - packed decimal PIB - positive integer binary PK - packed unsigned $n - standard character $CHAR - characters with blanks $HEX - character hexadecimal $VARYING - variable-length values
SASFIELD
PK1
Authorization Event Record

The following table shows each field available in the Connect:Direct Authorization Event record. The CDAER member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names AERECLN Field Description Length of this record.
Chapter 5 / ARS Record Layouts
5-3
Field Names AERTYPE
Field Description Record type indicates specific data in statistics record: IU=INSert; UU=UPDate USER; SU=SELect USER; and DU=DELete USER. Time that event was recorded in hh/mm/ss/tt format. Date that event was recorded in Julian date format (yyyydddf). Process name. Process number. User node of the submitter. Userid of the submitter. Step name or label. Time that Process started in hh/mm/ss/tt format. Date that Process started in Julian date format (yyyydddf). Step completion code. Message ID. Length of data set name. Source data set name. Data set type (LIB, DSN). Event code. Event code qualifier.
AERTIME AEDATE AEPROCNM AEPROCNO AEUNODE AEUID AESTEP AESTIME AESDATE AESCC AEMSGID AESDSNL AESDSN AESDSTYP AEEVENT AEEVENTQ
Change Process Termination Record

The following table shows each field available in the Connect:Direct Change Process Termination record. The CDCPTR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names CHRECLN CHRTYPE CHTIME CHDATE Field Description Length of this record. Record type CH indicates the Change Process Termination Record. Time that CHange PROCess command completed in hh/mm/ss/tt format. Date that CHange PROCess command completed in Julian date format (yyyydddf). Process name. Process number. Step name or label. User node ID of the submitter.
CHPROCNM CHPROCNO CHSTEP CHUNODE
5-4
Field Names CHUID CHSTIME CHSDATE
Field Description Userid of the submitter. Time that CHange PROCess command started in hh/mm/ss/tt format. Date that CHange PROCess command started in Julian date format (yyyydddf). Step completion code-displays normal completion code. Message ID. Node where message routed. Userid where message routed. Time that Process was scheduled in hh/mm/ss/tt format. Date that Process was scheduled in Julian date format (yyyydddf). Day that Process was scheduled. New Process priority in the Connect:Direct Transmission Control Queue (TCQ). Keeps copy in TCQ after execution. ALL/PROCNAME/PROCNUMBER. New destination node. Process status in hold queue: Q=quiesce or I=immediate. New priority. Release Processes=R. Retain Processes=R. New node ID messages to be routed. New userid messages to be routed. New scheduled time in hh/mm/ss/tt format. New scheduled date in Julian date format (yyyydddf).
CHSCC CHMSGID CHRMNID CHRMUID CHSCHTME CHSCHDTE CHSCHDAY CHPRTY
CHRETAIN CHPROC CHNDEST CHHOLD CHNPRTY CHREL CHRET CHNRMNID CHNRMUID CHNEWTME CHNEWDTE
Copy Termination Record

The following table shows each field available in the Connect:Direct Copy Termination record. The CDCTR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names CTRECLN CTRTYPE CTTIME FIeld Description Length of this record. Record type CT indicates the Copy Termination record. Time that COPY step completed in hh/mm/ss/tt format.
5-5
Field Names CTDATE CTSTIME CTSDATE CTSCC CTMSGID CTPROCNM CTPROCNO CTSTEP CTUNODE CTUID CTPNODE CTSNODE CTNODE CTFROM CTTRANS
FIeld Description Date that COPY step completed in Julian date format (yyyydddf). Time that COPY step started in hh/mm/ss/tt format. Date that COPY step started in Julian date format (yyyydddf). Step completion code. Displays normal completion code. Message ID. Process name. Process number. Step name or label. User node ID of the submitter. Userid of the submitter. Name of the node which is examining its Connect:Direct statistics file. Name of the other node. This node is P(node) or S(node). Direction of data: Snode to Pnode or Pnode to Snode File translation. Includes: ASCII-TO-EBCDIC; EBCDIC-TO-ASCII; EBCDIC-TO-ASCII DIF; compressed; and compacted. Transmission options. Includes: PDS-to-PDS copy; error originated on other node; sending PDS member to sequential DSN; sending DSN sequential DSN to PDS member; and COPY is restarted. Request/response unit (RU) size. Displacement to Pnode account data length. Displacement to Snode account data length. Number of bytes read from data set. Number of records read from data set. Number of blocks read from data set. Number of bytes sent. Number of bytes written to data set. Number of records written to data set. Number of blocks written to data set. Number of bytes received. Number of kilobytes sent. Number of members sent. Number of aliases sent. Number of members selected but not sent. Number of aliases selected but not sent.
CTTRANS2
CTRUSZ CTPACCT# CTSACCT# CTINBYTE CTINRECN CTINBLK CTSBYTES CTOBYTE CTOTRECN CTOTBLK CTRBYTES CTNOKB CTNOMEMS CTNOALIS CTNOMEMX CTNOALIX
5-6
Field Names CTNOMEMR CTNOALIR CTCMPTBL CTSDSTYP CTSDISP1 CTSDISP2 CTSDISP3 CTSDSNL CTSDSN CTDDSTYP CTDDISP1 CTDDISP2 CTDDISP3
FIeld Description Number of members received. Number of aliases received. The compaction table name. Source data set type: ESDS, KSDS, RRDS, PDS, SAM, or LIB. Source data set disposition status: O=OLD and S=SHR. Source data set disposition normal termination: D=DELETE and K=KEEP. Source data set disposition abnormal termination: D=DELETE and K=KEEP. Length of the source data set name. Source data set name. Destination data set type. Destination data set disposition status: M=MOD; N=NEW; O=OLD; and S=SHR. Destination data set disposition normal termination: C=CATLG and K=KEEP. Destination data set disposition abnormal termination: C=CATLG; K=KEEP; and D=DELETE. Length of destination data set name. Destination data set name. Member name for PS to PO copies. Message ID from other node. Return code from other node. Number of VTAM sends. Number of VTAM receives. Displacement of receiving VOLSER list. Displacement of sending VOLSER list TCP buffer size used. V2 buffer size. Negotiated V2 buffer size.
CTDDSNL CTDDSN CTMEMBER CTOMSGID CTRTNCD CTNVTAMS CTNVTAMR CTDSPVLR CTDSPVLS CTTBOFS CTV2BUFS CTNEGBF
5-7
Delete Process Termination Record

The following table shows each field available in the Connect:Direct Delete Process Termination record. The CDDPTR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names DPRECLN DPRTYPE DPTIME DPDATE DPPROCNM DPPROCNO DPSTEP DPUNODE DPUID DPSTIME DPSDATE DPSCC DPMSGID DPDPRNM DPDPRNOP DPRMNID DPRMUID Field Description Length of this record. Record typeDP indicates the Delete Process Termination record. Time that DELete PROCess command completed in hh/mm/ss/tt format. Date that DELete PROCess command completed in Julian date format (yyyydddf). Process name. Process number. Step name or label. User node iD of the submitter. Userid of the submitter. Time that DELete PROCess command started in hh/mm/ss/tt format. Date that DELete PROCess command started in Julian format (yyyydddf). Step completion code. Displays normal completion code. Message ID. Name of the deleted Process. Number of the deleted Process. Route message node of deleted Process. Route message userid of deleted Process.
Display Statistics Record

The following table contains each field available in the Connect:Direct Display Statistics record. The CDDTR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Name DTRECLN DTRTYPE Field Description Length of this record. Record type indicates specific data in statistics record: SP=SELect PROCess; DT=SELect TASK; FT=FLUSH TASK; SS=SELect STATistics; and SN=SELect NETMAP. Time that command completed in hh/mm/ss/tt format. Date that command completed in Julian date format (yyyydddf).
DTTIME DTDATE
5-8
Field Name DTPROCNM DTPROCNO DTSTEP DTUNODE DTUID DTSTIME DTSDATE DTSCC DTMSGID DTDFLNM DTNVTAMS DTNVTAMR DTGETS DTPUTS
Field Description Process name. Process number. Step name or label. User node ID of the submitter. Userid of the submitter. Time that command started in hh/mm/ss/tt format. Date that command started in Julian date format (yyyydddf). Step completion code. Displays normal completion code. Message ID. Name of the displayed data set. Number of VTAM sends. Number of VTAM receives. Number of GETS. Number of PUTS.
Flush/Suspend Process Termination Record

The following table shows each field available in the Connect:Direct Flush Process/Suspend Process Termination record. The CDFPTR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names FPRECLN FPRTYPE FPTIME FPDATE FPPROCNM FPPROCNO FPSTEP FPUNODE FPUID FPSTIME FPSDATE Field Description Length of this record. Record typeFP indicates the Flush Process Termination record. Time that FLUSH PROCess command completed in hh/mm/ss/tt format. Date that FLUSH PROCess command completed in Julian date format (yyyydddf). Process name. Process number. Step name or label. User node ID of the submitter. Userid of the submitter. Time that FLUSH PROCess command started in hh/mm/ss/tt format. Date that FLUSH PROCess command started in Julian date format (yyyydddf).
5-9
Field Names FPSCC FPMSGID FPDPRNM FPDPRNOP FPRMNID FPRMUID
Field Description Step completion code. Displays normal completion code. Message ID. Name of the flushed Process. Number of the flushed Process. Route message node of flushed Process. Route message userid of flushed Process.
PDS Member Copy Record

The following table shows each field available in the Connect:Direct PDS Member Copy record. The CDFMCR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names MCRECLN MCRTYPE MCTIME MCDATE MCSTIME MCSDATE MCSCC MCMSGID MCPROCNM MCPROCNO MCSTEP MCUNODE MCUID MCPNODE MCSNODE MCNODE MCFROM MCTNAME MCFNAME MCANAME Field Description Length of this record. Record typeMC indicates the PDS Member Copy record. Time that COPY step completed in hh/mm/ss/tt format. Date that COPY step completed in Julian date format (yyyydddf). Time that member processing started in hh/mm/ss/tt format. Date that member processing started in Julian date format (yyyydddf). Step completion code. Displays normal completion code. Message ID. Process name. Process number. Step name or label. User node ID of the submitter. Userid of the submitter. The Pnode name for this Process. The Snode name for this Process. This node is P(node) or S(node). Direction of data: P(node) to Snode or S(node) to Pnode. Name of member on destination PDS. Name of member on source PDS (if different). Name of member for which node is an alias.
5-10
Field Names MCNRECS MCNBLKS
Field Description The number of records. The number of blocks.
Process Submit Statistics Record

The following table shows each field available in the Connect:Direct Process Submit Statistics record. The CDPSSR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names PSSRECLN PSSRTYPE Field Description Length of this record. Record type indicates specific data in statistics record: PS=SUBmit statement and SW=SUBmit command within a Process. Time that Process completed in hh/mm/ss/tt format. Date that Process completed in Julian date format (yyyydddf). Time that Process started in hh/mm/ss/tt format. Date that Process started in Julian date format (yyyydddf). Step completion code. Displays normal completion code. Message ID. Process name. Process number. Step name or label. Submitters symbolic node name. Userid of the submitter. Pnode name for this Process. Snode name for this Process. This node is P(node) or S(node). Direction of data: P(node) to Snode or S(node) to Pnode. The number of bytes in the Process. Route message userid of Process. The function code for the SUBMIT. The syntax error in SUBmit command. The parse error in SUBmit command. Displacement to Pnode account data.
PSSCTIME PSSCDATE PSSSTIME PSSSDATE PSSSCC PSSMSGID PSSPRCNM PSSPRCNO PSSSTEP PSSUNODE PSSUID PSSPNODE PSSSNODE PSSNODE PSSFROM PSSROSIZ PSSRMNID PSSFUNCD PSSSYNTX PSSPARSE PSSPACT#
5-11
Field Names PSSSACT# PSSDSN#
Field Description Displacement to Snode account data. Displacement to data set name.
Process Termination Record

The following table shows each field available in the Connect:Direct Process Termination record. The CDPTR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names PTRECLN PTRTYPE PTTIME PTDATE PTSTIME PTSDATE PTSCC PTMSGID PTPROCNM PTPROCNO PTSTEP PTUNODE PTUID PTPNODE PTSNODE PTNODE PTFROM PTUNPRNO PTRMNID PTRMUID PTSUBTME PTSUBDTE PTSCHTME PTSCHDTE Field Description Length of this record. Record typePT indicates the Process Termination record. Time that Process completed in hh/mm/ss/tt format. Date that Process completed in Julian date format (yyyydddf). Time that Process started in hh/mm/ss/tt format. Date that Process started in Julian date format (yyyydddf) Step completion code. Displays normal completion code. Message ID. Process name. Process number. Step name or label. Submitters symbolic node name. Userid of the submitter. Pnode name for this Process. Snode name for this Process. This node is P(node) or S(node). Direction of data: P(node) to Snode or S(node) to Pnode. Process number unique to submitters node. Route message userid of Process. Userid where message is routed. Time that Process was submitted in hh/mm/ss/tt format. Date that Process submitted in Julian date format (yyyydddf). Time that Process was scheduled in hh/mm/ss/tt format. Date that Process was scheduled in Julian date format (yyyydddf).
5-12
Field Names PTSCHDAY PTSTMTN PTPRTY
Field Description Day Process was scheduled. Number of statements. Process selection priority.
Run Job Termination Record

The following table shows each field available in the Connect:Direct Run Job Termination record. The CDRJTR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names RJRECLN RJRTYPE RJTIME RJDATE RJSTIME RJSDATE RJSCC RJMSGID RJPROCNM RJPROCNO RJSTEP RJUNODE RJUID RJPNODE RJSNODE RJNODE RJFROM RJJOBNM RJJOBNO RJSYRCD RJDDSN RJPACCT# RJSACCT# Field Description Length of this record. Record typeRJ indicates the Run Job Termination record. Time that RUN JOB step completed in hh/mm/ss/tt format. Date that RUN JOB step completed in Julian date format (yyyydddf). Time that RUN JOB step started in hh/mm/ss/tt format. Date that RUN JOB step started in Julian date format (yyyydddf). Step completion code. Displays normal completion code. Message ID. Process name. Process number. Step name or label. Submitters symbolic node name. Userid of the submitter. Pnode name for this Process. Snode name for this Process. This node is P(node) or S(node). Direction of data: P(node) to Snode or S(node) to Pnode. Job name. Job number. System return code. Displacement to data set name. Displacement to Pnode account data. Displacement to Snode account data.
5-13
Run Task Termination Record

The following table shows each field available in the Connect:Direct Run Task Termination record. The CDRTTR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names RTRECLN RTRTYPE RTTIME RTDATE RTSTIME RTSDATE RTSCC RTMSGID RTPROCNM RTPROCNO RTSTEP RTUNODE RTUID RTPNODE RTSNODE RTNODE RTFROM RTMODNM RTSYSRTN RTPARMLN RTPACCT# RTSACCT# Field Description Length of this record. Record typeRT indicates the Run Task Termination record. Time that RUN TASK step completed in hh/mm/ss/tt format. Date that RUN TASK step completed in Julian date format (yyyydddf). Time that RUN TASK step started in hh/mm/ss/tt format. Date that RUN TASK step started in Julian date format (yyyydddf). Step completion code. Displays normal completion code. Message ID. Process name. Process number. Step name or label. Submitters symbolic node name. Userid of the submitter. Pnode name for this Process. Snode name for this Process. This node is P(node) or S(node). Direction of data: P(node) to Snode or S(node) to Pnode. Name of the RUN TASK program. System return code. Length of the parameter list. Displacement to Pnode account data. Displacement to Snode account data.
5-14
Signon/Signoff Statistics Record

The following table shows each field available in the Connect:Direct Signon/Signoff Statistics record. The CDSFR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names SIRECLN SIRTYPE Field Description Length of this record. Record type indicates specific data in the statistics record: SI=SIGNON command and SO=SIGNOFF command. Time that SIGNON/SIGNOFF command completed in hh/mm/ss/tt format. Date that SIGNON/SIGNOFF command completed in Julian date format (yyyydddf). User symbolic node ID. Userid of the submitter. Step completion code. Displays normal completion code. Message ID.
SITIME SIDATE SIUNODE SIUID SISCC SIMSGID
Start Connect:Direct Command Record

The following table shows each field available in the Start Connect:Direct Command record. The CDSDCR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names SDRECLN SDRTYPE SDTIME SDDATE SDPROCNM SDPROCNO SDSTEP SDUNODE SDUID SDSTIME SDSDATE SDSCC SDMSGID Field Description Length of this record. Record typeSD indicates the Start Connect:Direct Command record. Time that Start Connect:Direct command completed in hh/mm/ss/tt format. Date that Start Connect:Direct command completed in Julian date format (yyyydddf). Process name. Process number. Step name or label. Submitters symbolic node name. Userid of the submitter. Time that Start Connect:Direct command was issued in hh/mm/ss/tt format. Date that Start Connect:Direct command was issued in Julian date format (yyyydddf). Step completion code. Displays normal completion code. Message ID.
5-15
Stop Connect:Direct Statistics Record

The following table shows each field available in the Stop Connect:Direct Statistics record. The CDSTDCR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names TDRECLN TDRTYPE TDTIME TDDATE Field Description Length of this record. Record typeST indicates the Stop Connect:Direct Statistics record. Time that STOP Connect:Direct command completed in hh/mm/ss/tt format. Date that STOP Connect:Direct command completed in Julian date format (yyyydddf). Process name. Process number. Step name or label. User node of the submitter. Userid of the submitter. Time that STOP Connect:Direct command was issued in hh/mm/ss/tt format. Date that STOP Connect:Direct command was issued in Julian date format (yyyydddf). Step completion code. Displays normal completion code. Connect:Direct shutdown types: W=Step shutdown; X=Immediate shutdown; Y=Quiescent shutdown; and Z=Forced shutdown by an abend. Message ID.
TDPROCNM TDPROCNO TDSTEP TDUNODE TDUID TDSTIME TDSDATE
TDSCC TDSTOP
TDMSGID
Stop Session Statistics Record

The following table shows each field available in the Connect:Direct Stop Session Statistics record. The CDSTSR member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names TSRECLN TSRTYPE TSTIME TSDATE FIeld Description Length of this record. Record typeTS indicates the Stop Connect:Direct Statistics record. Time that STOP Connect:Direct command completed in hh/mm/ss/tt format. Date that STOP Connect:Direct command completed in Julian date format (yyyydddf). Process name.
TSPROCNM
5-16
Field Names TSPROCNO TSSTEP TSUNODE TSUID TSSTIME TSSDATE TSSCC TSMSGID TSPNODE TSSNODE
FIeld Description Process number. Step name or label. User node of the submitter. Userid of the submitter. Time that stop session was issued in hh/mm/ss/tt format. Date that stop session was issued in Julian date format (yyyydddf). Step completion code. Displays normal completion code. Message ID. Pnode symbolic node. Snode symbolic node.
Write to Operator (WTO) Statistics Record

The following table shows each field available in the Connect:Direct WTO Statistics record. The CDFWTOST member of the $CD.MAPLIB library contains the SAS maps of the Connect:Direct statistics record.
Field Names WTRECLN WTRTYPE WTCTIME WTCDATE WTSTIME WTSDATE WTSCC WTMSGID WTPROCNM WTPROCNO WTSTEP WTUNODE WTUID WTPNODE WTSNODE WTNODE Field Description Length of this record. Record typeWT indicates the WTO Statistics record. Time that Process completed in hh/mm/ss/tt format. Date that Process completed in Julian date format (yyyydddf). Time that function started in hh/mm/ss/tt format. Date that function started in Julian date format (yyyydddf). Step completion code. Displays normal completion code. Message ID. Process name. Process number. Step name or label. Submitters symbolic node name. Userid of the submitter. The Pnode name for this Process. The Snode name for this Process. This node is P(node) or S(node).
5-17
Field Names WTFROM WTTASKNO
Field Description Direction of data: P(node) to Snode or S(node) to Pnode. Task number that issued the WTO.
5-18
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 Activity Reporting System Users 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
Symbols
$HLQ.ARS.MAPLIB contents 5-1 DMAER member 5-2 DMCPTR member 5-3 DMCTR member 5-4 DMDPTR member 5-7 DMDTR member 5-7 DMFMCR member 5-9 DMFPTR member 5-8 DMFWTOST member 5-16 DMPSSR member 5-10 DMPTR member 5-11 DMRJTR member 5-12 DMRTTR member 5-13 DMSDCR member 5-14 DMSFR member 5-14 DMSTDCR member 5-15 DMSTSR member 5-15 %INCLUDE 4-4
ARS Reports (continued) requesting 2-1 requesting through a Process 1-1 requesting through a scheduling subsystem requesting through screens 3-1 using 1-1 ARS Screens accessing 3-3 ARS screens accessing 3-3 accessing through IUI 3-2 Connect:Direct Requirements example 3-5 field descriptions 3-5 Report Options example 3-3 field descriptions 3-4 SAS Requirements example 3-6 field descriptions 3-6 signon parameters 3-3 using 3-1 Authorization Event record 5-2
1-1
A
Activity Reporting System (ARS) business solutions 1-2 description 2-1 example 2-1 field descriptions 2-2 in conjunction with Connect:Direct 1-1 system requirements 1-2 tracking Connect:Direct activities 1-2 ARS Reports customizing 5-1 methods of requesting 1-1, 2-1 multiple reports job stream definitions 4-3 routing to output data sets 4-5 sample job stream 4-2 sample Process to submit job stream
B
Business solutions 1-2
C
Capacity planning 1-3 5-3 Change Process Termination record Connect:Direct description 1-1 utilization 1-3 Copy Termination record Customizing ARS Reports 4-5 5-4 5-1
Index-2
D
Data center management 1-2 2-7 Data set access security failures DATA SET NAME CONTAINING SAS ROUTINES 3-6 Delete Process Termination record Display Statistics record DMBATCH DMMSGFIL DMPRINT DMPUBLIB 4-3 4-4 4-4 4-4 5-7 5-7
Field descriptions (continued) Submit Within a Process Report Summary Report 2-3
2-15 5-8
Flush Process/Suspend Process Termination record FT20F001 4-4
Function Reports description 1-2, 2-8 Non-PDS Copy Report 2-8 PDS Copy Report 2-8 Run Job Report 2-8 Run Task Report 2-8 Submit Within a Process Report types of 1-2, 2-8
2-8
E
Examples Activity Report 2-1 ARS Connect:Direct Requirements screen ARS Report Options screen 3-3 ARS SAS Requirements screen 3-6 Exception Report 2-5 Non-PDS Copy Report 2-9 PDS Copy Report 2-11 Run Job Report 2-13 Run Task Report 2-14 Security Violations Report 2-7 Submit Within a Process Report 2-15 Summary Report 2-3 Exception Report description 2-5 example 2-5 field descriptions 2-6 problem isolation 1-3 use 1-1 3-5
J
Job stream modifying for multiple reports 4-2 producing ARS reports 3-1 SAS options 4-3 submitting 4-5 submitting to create reports 3-7 viewing from screen 3-7 Job stream definitions JOBCARD INFO 3-5, 4-3 4-3
M
MESSAGE DATA SET NAME 3-5 Multiple reports job stream definitions 4-3 modifying the sample job stream 4-2 routing to an output data set 4-5 sample job stream 4-2 sample Process to submit job stream 4-5
F
Field descriptions Activity Report 2-2 ARS Connect:Direct Requirements screen ARS Report Options screen 3-4 ARS SAS Requirements screen 3-6 Exception Report 2-6 Non-PDS Copy Report 2-9 PDS Copy Report 2-11 Run Job Report 2-13 Run Task Report 2-14 Security Violations Report 2-7 NDMX0001 3-5 4-4 Non-PDS Copy Report description 2-8 example 2-9 field descriptions 2-9
O
OUTPUT (SYSOUT) CLASS Output data sets 4-5 3-6
Index-3
P
PDS Copy Report description 2-10 example 2-11 field descriptions 2-11 PDS Member Copy record Prerequisites 1-2 1-3 2-7 5-10 5-9
Security Violations Report description 1-1, 2-7 example 2-7 field descriptions 2-7 types of failures reported use 1-2 Signon security failures 2-7
2-7
Signon/Signoff Statistics record
5-14 5-14
Problem isolation
Start Connect:Direct Command record START DATE START TIME STEPLIB 3-5 4-4 3-5 5-11 3-4 3-4
Process security failures
Process Submit Statistics record Process Termination record
PUBLIC PROCESS LIBRARIES
STEPLIB DATA SET NAME
R
Run Job Report description 2-13 example 2-13 field descriptions 2-13 Run Job Termination record Run Task Report description 2-14 example 2-14 field descriptions 2-14 Run Task Termination record 5-13 5-12
Stop Connect:Direct Command record STOP DATE 3-4 5-15
5-15
Stop Session Statistics record STOP TIME 3-4
Submit Within a Process Report description 2-15 example 2-15 field descriptions 2-15 Summary Report capacity planning 1-3 description 2-3 example 2-3 field descriptions 2-3 use 1-3 4-5 SYSIN 4-4 4-4 1-1
S
Sample Process to submit job stream SAS Informat variables 5-1, location of maps 5-1 prerequisites 1-2 5-2
SYSPRINT
System Management Facility
SAS CATALOGED PROCEDURE SASPROGS SASTEP 4-4 4-4
3-6 TEMPDSN 4-4 1-1 Time Sharing Option
Screens ARS Connect:Direct Requirements ARS Report Options 3-3 ARS SAS Requirements 3-6
3-5 WORK 4-4
W
Write to Operator (WTO) Statistics record 5-16
Security subsystems CA-ACF2 2-7 IBM Resource Access Control Facililty Security violations 1-2
2-7
Index-4

Ars User Guide

Uploaded by

Document Information

Original Description:

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

Ars User Guide

Uploaded by

Copyright:

Available Formats

PN 00738

Activity Reporting System Users Guide

About the Activity Reporting System

ARS Report Examples

Connect:Direct OS/390 Activity Reporting System Users Guide

Requesting ARS Reports Using Screens

Requesting Multiple ARS Reports or Scheduled Processing

ARS Record Layouts

Connect:Direct OS/390 Activity Reporting System Users Guide

Connect:Direct OS/390 Documentation

Getting Support for Sterling Commerce Products

Connect:Direct OS/390 Activity Reporting System Users Guide

About the Activity Reporting System

Using Activity Reports

ARS and Connect:Direct

Connect:Direct OS/390 Activity Reporting System Users Guide

Requesting ARS Reports

Business Solutions Using ARS

Chapter 1 / About the Activity Reporting System

Function Capacity Planning

Connect:Direct OS/390 Activity Reporting System Users Guide

ARS Report Examples

You can request these reports in the following ways:

Connect:Direct Activity Report

Connect:Direct OS/390 Activity Reporting System Users Guide

The following table contains a description of the report fields.

ELAPSE TIME PNODE CC EXC MSG ID DATE

Chapter 2 / ARS Report Examples

Connect:Direct Summary Report

The following table contains a description of the report fields.

Connect:Direct OS/390 Activity Reporting System Users Guide

Report Field FIRST FUNCTION

Number of SUBMIT (within a Process) steps submitted to run at NODE.

Total number of successful steps. Percentage of total successful steps.

Total number of unsuccessful steps. Percentage of total unsuccessful steps.

WAS AVERAGE TIME TO COMPLETE A FUNCTION WAS TOTALCOPY TIME

Chapter 2 / ARS Report Examples

EFFECTIVE RECEIVE RATE

Connect:Direct Exception Report

CD EXCEPTION REPORT NODE = CD.BOSTON

Connect:Direct OS/390 Activity Reporting System Users Guide

(SUBMIT) Data set containing Process.

(SUBMIT) Intended node location where the Process is submitted.

Chapter 2 / ARS Report Examples

Connect:Direct Security Violations Report

A sample report follows.

The following table contains a description of the report fields.

Connect:Direct OS/390 Activity Reporting System Users Guide

Report Field MSG ID DATE TIME VIOLATION TYPE

Connect:Direct Function Reports

Connect:Direct NonPDS Copy Report

Chapter 2 / ARS Report Examples

Following is an example of the Connect:Direct NonPDS Copy Report.

COMPLETION CODE MSG ID message

Connect:Direct OS/390 Activity Reporting System Users Guide

Connect:Direct PDS Copy Report

PDS data set <--------> PDS data set

Chapter 2 / ARS Report Examples

Following is an example of the Connect:Direct PDS Copy Report.

COMPLETION CODE MSG ID message

Connect:Direct OS/390 Activity Reporting System Users Guide

Chapter 2 / ARS Report Examples

Connect:Direct Run Job Report