Home

Unicenter CA-XCOM Data Transport for z/OS User Guide

1. ICI ISIS ICI II IC III A FR GLOBAL EXEC PGM IEBDG SYSPRINT DD SYSOUT GLOBAL DD DSN XXXXXXXX GLOBAL lt 2 VOL SER VVVVVV lt 3 UNIT SYSALLDA DISP NEW CATLG DELETE 1 DCB RECFM F LRECL 80 BLKSIZE 80 SYSIN DD DSD OUTPUT GLOBAL CREATE QUANTITY 1 FILL X 00 RESTART EXEC PGM IEBDG SYSPRINT DD SYSOUT RESTART DD DSN XXXXXXXX RESTART lt 4 VOL SER VVVVVV lt 5 UNIT SYSALLDA DISP NEW CATLG DELETE SPACE TRK 1 DCB RECFM F LRECL 2020 BLKSIZE 2020 SYSIN DD DSD OUTPUT RESTART CREATE QUANTITY 1 FILL X 00 Sample Files 9 Sample JCL for Defining the Inquire Data Set Member DEFINQ Sample JCL for Defining the Inquire Data Set Member DEFINQ The following is a copy of the sample DEFINQ Job found on the distribution tape CALCINBOSAM DEFINQ JOBNAME JOB ACCOUNTING XCOM INSTALLATION lt 1 CLASS X MSGCLASS X MSGLEVEL 1 1 BOBO IOI K k K k K KOK K K DOC CREATE XCOMJOB INQUIRY SEQUENTIAL FILE FOR TYPE SCHEDULE CHANGE 1 SUPPLY A VALID JOBCARD FOR YOUR INSTALLATION 2 DATASET NAME TO BE USED FOR YOUR INQUIRY DATASET d
2. THE FOLLOWING SYSMDUMP DD STATEMENT DEFINES A SYSTEM DUMP DATA SET THIS DATA SET SHOULD BE GIVEN THE SAME SPACE ALLOCATIONS AS THE SYS1 DUMPNN DATASETS IN USE AT YOUR SITE K k K K k K k K K K kK k k k K K k k SYSMDUMP DD DSN amp PREFIX SYSMDUMP DISP SHR SYSTEM DUMP C 20 User Guide Sample Unicenter CA XCOM Data Transport Server JCL Member Sample Unicenter CA XCOM Data Transport Server JCL Member XCOM This member contains a sample Unicenter CA XCOM Data Transport JCL found on the distribution tape CALCINBOSAM XCOM This JCL illustrates the definition of the Unicenter CA XCOM Data Transport XCOMPLEX Worker or standalone server Note With Unicenter CA XCOM Data Transport for z OS it is no longer necessary to specify Interlink libraries Specify the correct name for TCPSTACK as a PARM parameter in the Unicenter CA XCOM Data Transport Default Options Table XCOM PROC PREFIX XCOM RBO HIGH LEVEL DATA SET NAME QUAL IAG CA XCOM FOR MVS SERVER ADDRESS SPACE X OBO SERVER EXEC PGM XCOMXFER TIME 1440
3. CA XCOM FOR MVS SAMPLE SYSTEM ADMINISTRATOR TABLE FOLLOWING ACCESS PARAMETERS ARE AVAILABLE SUSP SUSPEND TRANSFER RESM RESUME SUSPENDED TRANSFERS HOLD HOLD TRANSFERS REL RELEASES HELD TRANSFERS E TERM ACTIVE TRANSFERS 8 DEL DELETE TRANSFER REQUESTS FROM SCHEDULED REQUESTS QUEUE ALT ALTER START DATE TIME AND EXECUTION PRIORITY DACT DISPLAY ACTIVE TRANSFERS d DSCH DISPLAY SCHEDULED TRANSFERS DHST DISPLAY HISTORY OF TRANSFERS PRINT GE ADMTAB ADMIN XCOMO3 GROUP 55 ALL ADMTAB ADMIN XCOMO6 GROUP 55 DSCH DHST SUSP ALT GLOBALADMIN ADMTAB ADMIN XCOMO7 GROUP XCOM ACCESS SUSP RESM HOLD REL TERM DEL ALT DSCH DHST ADMTAB ADMIN XCOM10 GROUP XCOM1 ACCESS DSCH DHST ALL END XCOMADMT Sample Files Sample XCPF Member XCPF Sample XCPF Member XCPF C 18 User Guide This sample JCL shows how to define an XCOMPLEX to the IBM Coupling Facility This is found on the distribution tape see CAI CINBOSAM XCPF JOBNAME JOB ACCOUNTING DEFINE SYSPLEX CLASS A MSGCLASS X IF YOU HAVE MORE THAN ONE VOLUME SEPARATE THE PRIMARY AND ALTERNATE DATASETS OR JUST RUN WITH A PRIMARY IF DESIRED J RRR RR KK OK K
4. 5 9 Using PSOWATE 55045 REESE oA Rede Sed ed ERES 5 9 JES2 Cornstderatiofis ETE EE AREER 5 10 Valid Destination 2 2 24 2 2 2 5 10 JES3 Considerations 2 2 2 5 10 Valid Destination 2 2 2 2 5 10 Sample Specific Destination 5 11 Sample Generic Destination Definition 2 5 11 PSOPREF Considerations cea awa teet 5 12 Format for PSO Data Set Names 5 12 Determining the User Catalog for the Unicenter CA XCOM Data Transport PSO Interface 5 13 Chapter 6 Operation and Control Starting the Unicenter CA XCOM Data 6 1 Starting the Unicenter CA XCOM Data Transport XCOMPLEX Admin Server 6 2 Starting the Unicenter CA XCOM Data Transport XCOMPLEX Worker Server 6 3 Using the Unicenter CA XCOM Data Transport MODIFY 8 6 4 MODIFY Command Format i21 ere Lee ERR
5. 6 29 NOTRACE 6 30 NOXTRACE Command 2 42 6 31 NSASTAT Command 4 2 24 2 6 32 RELEASE Command xis idee feces E qu sasa pase p ata 6 33 RESET Command 2 24 2 6 34 RESUME Commands evt oeste due Saone e doce onan Ead snes Ard dU dbi qe 6 35 RSHOW Command 2 2 4 24 24 6 36 SHOW Commande cemeterio oo exor eM Leu UM EUN ccm tcl 6 38 SNAP Command 4 2 6 39 STAT Command 2 2 2 2 2 2 2 6 40 STOP Command sin ojo bo opto oet ib petu pu tube bas 6 42 SUSPEND Commands Ac cnc emer teet ror tUm ccs ener e 6 44 TERM 6 45 TRACE Command 6 47 VERSION Dec ERU E Eau de Re be Ries 6 48 ARSOHOW COMMANG 42324434304 25654040 40500006 aan red PARERE dE 6 49 XSHOW Command ieetencterebeneberebereberebeDebesebteretereberebsenesierepeseP
6. 3 62 SYSIN01 Tape Parameters sin iia tt ceca aie 3 67 SYSINO1 DCB 2 2 2 4 3 72 SYSINO1 Transfer Control XTC 3 74 Coding Interdependent 3 79 Coding XTC Transfers in an XCOMPLEX 3 81 XCOMJOB Return Codes 3 82 Chapter 4 The Programming Interface The Unicenter CA XCOM Data Transport Process 4 1 Allocating the Local Data Set and Parameter 4 2 Define Two Unicenter CA XCOM Data Transport Files 4 2 Sample DD Statement E a a a 4 2 Calling Unicenter Data Transport from a COBOL Program 4 3 Sample 4424 404444645436 phe ere ebbe iub olet bed eben 4 3 Contents v Calling Unicenter CA XCOM Data Transport from an Assembler Program 4 5 Sample Assembler Propran quao eun SA Va ade E naa Sa 4 5 Chapter 5 The Remote Spooling Feature Process SYSOUT Basics OF JES Spool sedere tree
7. sample JCL C 41 XCOMTOPS assembling C 31 user security exit sample JCL C 31 XCOMUP2F user exit calling module D 21 XCOMUPLA user exit calling module D 21 XCOMUPLG6 user exit calling modules D 21 XCOMUTIL history file purge utility 2 parameters B 3 AGE B 3 DATE B 4 PROCESS B 4 required JCL B 5 sample JCL B 5 XCOMUTIL sample JCL C 6 XCOMXFER user exit calling module D 2 D 17 D 19 XCPF defining XCOMPLEX structure sample JCL C 19 XCOMPLEX definition to Coupling Facility sample JCL C 18 XFERID attribute label 2 116 XID attribute label 2 116 XRSHOW MODIFY command 6 49 XSHOW MODIFY command 6 51 XIC 3 74 coding example 3 79 XTCERRDECR SYSINOT parameter 3 75 XTCERRINCR SYSINO1 parameter 3 76 XTCERRPURGE SYSINO1 parameter 3 76 XTCERRREL SYSINOT parameter 3 75 XTCGOODDECR SYSINOT parameter 3 76 XTCGOODINCR SYSINO1 parameter 3 77 XTCGOODPURGE SYSINO1 parameter 3 77 XTCGOODREL SYSINO1 parameter 3 77 XTCJOB SYSINO1 parameter 3 77 XTCNET SYSINOT parameter 3 78 XTRACE MODIFY command 6 52 Index 17
8. iet e e e eek tach p te e Dawa beau 2 3 The Primary Option Menu clie mee t ee he ee eee RU Ee rk e EHI Re merkte 2 4 Selection Menu Options 2 2 4 2 2 5 Primary Processing Parameters operoi oriisgin re oe Hype v een Ure e ergo e een 2 6 Contents ili MVS Send Functions 2 14 Send Functions Menu Options 2 14 Send MVS File To Another System Screen 2 2 15 Parameter Fields su didn eu detur tud vou dudo aude dude eud edid utu 2 16 Remote System Information i i bie eiie pipi eii bipes 2 30 Local System Information 2229 eges on oe suus Vuvad qua aun dies nea eaa n Re aia DE 2 34 MVS Extended Tape Parameter Entry 2 4 2 38 pec rm 2 38 Parameter Fields 2 2 4 4 2 39 File Allocation Information Screen 225442252024 0004 a auo aka e aue a a n a Ra a a RV aA YT 2 41 Parameter Defaults 2 2 24 2 24 4 4 2 42 Supported File Types e e etel Ene eoe 2 42 AL M du E D M D E 2 42
9. TRANSID XCON PROGRAM XCICPRIM DTIMOUT 30 SPURGE YES TPURGE YES TRANSEC 01 TRMPRTY 100 TWASIZE 0 DFHPCT TRANSID XNTF PROGRAM XCICNTFY DTIMOUT 30 SPURGE YES TPURGE YES 5 01 TRMPRTY 100 TWASIZE 0 Sample Files 39 Sample XCOMPPT Sample XCOMPPT C 40 User Guide This member contains the CICS PPT entries to run the Unicenter CA XCOM Data Transport CICS MVS interface If you create the PPT entries through the COPYCSD step which copies directly from the Unicenter CA XCOM Data Transport provided CSD to the user CSD this member is not required If you do not use the COPYCSD step you must copy these entries into the CICS PPT and assemble the PPT before Unicenter CA XCOM Data Transport can be used meer M ME IEEE E ERI CICS PPT ENTRIES i m XCOM CICS MAPS DFHPPT TYPE ENTRY PROGRAM XCMPRIM PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMSEND PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMRFIL PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMSFIL PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMSRPT PGMLAN
10. 9 5 Types OF Piles SuppoOEted eres tenete dee tate E E Rue Sce Ue De puedo 9 5 DCDdnfOrmaton 9 5 Aden onal NAMES 9 6 Novell Ner aren sn 2 ns e SA LM 9 6 viii User Guide Naming Conventions iili 4445044 8404042 44448405044 344444404 9 6 Typesof Biles Supported suya u suave Ua Ua Wawel e adus nh aua aua qua Ma MARRE AU Mau qe qu 9 6 Destination Printer Information 2 2 2 9 7 Cons DP nm 9 7 OpenVMS E Ep ERE 9 8 Naming Conventions sesupe wav dua qua qu vag eu dua va veh di 9 8 RestrictionS c usai b PRSE RES Ib RM RE 9 9 05 2 cs dedu eicit duro eod dau ede uou ede du dud ied EE EEES 9 10 Naming ConyenbloliS osse sets te stets et pu met ue s pus md a e utes d gi d vineta 9 10 REStICHONS EPIIT 9 11 9 12 Naming Conventions uuu u 9 12 Types of Files ERROR e ee bee eai ed 9 13 Tanden de 9 14 Naming oou etude A 9 14 incu c E 9 14 Types Files Supported u ze reete eir nir ei en e c d Rer uS 9 15 File Type Specifica HoMe ce
11. bebe biis bid bt dd bs d bte bei D 10 MED Si TE Ohi ccs ulus au D 13 D 15 D 17 Exit E 19 uQ uwa a aus Zes D 21 User tob od obs D 23 WI SSPE Dod erdt D 25 Index xii User Guide Introduction This guide provides information about using Unicenter CA XCOM Data Transport for z OS Invoking Unicenter CA XCOM Data Transport Menu Interface Unicenter CA XCOM Data Transport is both easy to use and diverse enough for the most complex applications Data transfer can be completed through any one of three interfaces and reports can be printed on a remote printer using the Remote Spooling feature These are described fully in later chapters The menu interface provides a simple fill in the blanks approach to file transfer You are prompted for required information and can use the extensive on line help facilities provided with each product Unicenter CA XCOM Data Transport menus always have the look and feel appropriate to the system on which they are running For example the micro computer platforms use graphical user interfaces with menus tool bars pop up w
12. her nece RR Rc Rh his hun kunana 5 1 Advantages of Using the Process SYSOUT 5 1 luo 5 2 Overview Sending Reports with 5 2 5 3 Destination 2 4 5 5 Assigning a JES Destination or Writer to a Remote 5 6 Assigning a JES Destination or Writer to a Specific 5 6 Using Process SYSOUT with CICS or Other Online Systems 5 6 Using Process SYSOUT with 5 2 2 2 24 2 2 5 7 Sample z OS File Transfer toa PC etuer rt e v e I E ER 5 7 Sample z OS File Transfer toa 2 2 5 7 Process SYSOUT Enhancements yuyaya ay au eau nu Ue awn Salsa Vau aces Ua aM qnd a A away ied 5 8 External Writer 2 2 2 2 22 2 2 2 4 5 8 Reasons for Using the External Writer 5 8 Sample Sceflari Lote is Posi 115 05 4 5 8 Routing to a Specific Minicomputer Printer
13. 3 VOLUME UPON WHICH THE INQUIRY DATASET SHOULD RESIDE NOTE A SEPARATE INQUIRY DATA SET SHOULD BE DEFINED FOR EACH TYPE SCHEDULE JOB THEY ARE NOT SHARABLE THIS FILE MUST Jut ALSO BE PREALLOCATED IT SHOULD NOT BE CREATED IN THE SAME JOB STREAM AS THE SCHEDULE JOB T RR RRR KK KK KK KK KK KK KK KK ALLOC EXEC PGM IEBGENER SYSPRINT DD DUMMY SYSIN DD DUMMY SYSUT1 DD DUMMY DCB LRECL 80 BLKSIZE 800 RECFM FB DSORG PS SYSUT2 DD DSN XCOM REL XCOMINQ UNIT SYSDA DISP CATLG DCB LRECL 80 BLKSIZE 800 RECFM FB DSORG PS SPACE TRK 1 VOL SER VVVVVV Sample VTAM APPLID Definition Table Member APPLXCOM C 10 User Guide The following is a copy of the sample VTAM APPLID Definition Table found on the distribution tape CAI CINBOSAM APPLXCOM The table shows sample VTAM APPLID statements KKK K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K SAMPLE VTAM APPLID STATEMENTS PLEASE NOTE THAT Unicenter CA XCOM Data Transport FOR 2 05 NOW SUPPORTS PARALLEL SESSIONS THE PARSESS KEYWORD IN THE FIRST APPLID BELOW TURNS THIS SUPPORT ON IF YOU LEAVE THIS SET TO YES THEN THE PARTNER COMPUTERS MUST TURN ON THE APPROPRIATE SUPPORT FOR PARALLEL SESSIONS ON SIMILAR DEFINITIONS A NOTE ABOUT THE NAMES USED HERE X Sample VTAM APPLID
14. XCOMEXOI sample D 3 XCOMEX04 sample D 9 XCOMEX05 sample D 12 XCOMEX06 sample D 15 XCOMEX07 sample D 16 XCOMEX08 sample D 18 9 sample D 20 XCOMEX10 sample D 22 XCOMEX12 sample D 24 XCOMEX13 sample D 26 XCOMEXIT user exit calling module D 14 D 15 sample JCL C 38 XCOMFILE user exit calling module D 10 XCOMGLOB DD statement 3 7 XCOMHIST sample JCL C 3 XCOMINQ DD statement 3 7 sample JCL C 10 XCOMJOB 3 3 sample JCL 3 3 TYPE EXECUTE 3 3 TYPE EXECUTE JCL sample 24 TYPE INQUIRE 3 4 TYPE SCHEDULE 3 3 3 4 TYPE SCHEDULE JCL sample C 25 XCOMJOBE sample program C 24 XCOMJOBS sample program C 25 XCOMJOB parameters See PARM parameters and SYSINO1 parameters XCOMJOXI sample JCL C 28 XCOMJOXS sample JCL C 26 XCOMLSR sample JCL C 22 XCOMMODE sample entries C 12 XCOMOPER user exit calling module D 8 sample JCL 39 XCOMPLEX Admin Server sample JCL C 20 sample TYPE INQUIRE transfer C 28 sample TYPE SCHEDULE transfer C 26 starting 6 2 maximum entries operator control parameter 2 114 PARM parameter 3 28 sample JCL C 18 Worker Server starting 6 3 XCOMPPT sample JCL C 40 XCOMPSOI user exit calling module D 4 D 6 user exit calling module D 21 D 23 D 25 XCOMREST DD statement 3 7 sample JCL C 9 XCOMSAMP sample transaction C 23 XCOMTABL sample table C 12
15. ACFUSER ASXB AGE 10 ALERTS ALLOC CYLS APPLSEC DEFAULT BANNER YES CA7EXIT NO CATALOG YES CKPT 1000 CLASS A COMPNEG YES CONTIG DFLTVER 2 DIR 40 DLOGMOD VTAM DOMAIN DROPSESS NO DUMPCL A EDESC 0200 ENCRYPT NO EROUT 4020 ERRINTV 7 EXECUTE YES EXITO1 NO EXITO2 NO EXITO3 NO EXITO4 NO EXITO5 NO EXITO6 NO EXITO7 NO EXIT08 NO EXITO9 NO EXIT10 NO EXIT11 NO EXIT12 NO EXIT13 NO FERL 255 XC000070 VTAM ACB NAME FOR XCOM SERVER XXC000080 SOURCE CONTROL BLOCK FOR ACF2 USER IDXXCO00090 AGE AT WHICH TO PURGE LOCAL REQUESTS 000100 NETVIEW GENERIC ALERT CATEGORIES LVLSXXCO00110 ALLOCATION UNIT FOR DATASET CREATION 000120 SOURCE FOR RACINIT APPL PARAMETER 000130 ENABLE DISABLE BANNER PAGE FOR 000140 ENABLE DISABLE CA 7 INTERFACE 000150 CATALOG SUPPORT FOR DATASET CREATION 000160 CKPT COUNT DEFAULT 1000 IF OMITTED X SYSOUT CLASS FOR INCOMING REPORTS XXC000170 COMPRESSION NEGOTIATION 000180 RESERVED FOR FUTURE USE XXC000190 XCOM VERSION FOR USE W REMOTES XXC000200 DIRECTORY ALLOC FOR DATASET CREATIONXXCO00210 SOURCE OF VTAM MODE NAME XXC000220 DOMAIN NAME FOR WIN 2000 PRTNR 000220 SESSION DISPOSITION AT TRANSFER END 000230 DEFAULT SYSOUT CLASS FOR XCOM DUMPS 000240 WTO DESCRIPTOR CODES FOR ERROR MSGS 000250 ENABLE DISABLE ENCRYPTION SUPPORT XXC000260 WTO ROUTING CODES FOR ERROR MSGS
16. DD DSN SYS1 AMODGEN DISP SHR DD DSN SYS1 MODGEN DISP SHR SYSUT1 DD UNIT SYSALLDA SPACE 1700 6000 100 SYSUT2 DD UNIT SYSALLDA SPACE 1700 6000 100 SYSUT3 DD UNIT SYSALLDA SPACE 1700 6000 100 SYSPRINT DD SYSOUT SYSIN DD DSN CAT CINBOSAM XCOMACF2 DISP SHR SYSPUNCH DUMMY SYSOUT B SYSLIN DD DSN amp amp OBJSET DISP NEW PASS UNIT SYSALLDA SPACE 80 2000 500 LKED EXEC PGM IEWL COND 4 LE ASM PARM XREF LET LIST NCAL AC 1 NORENT NOREUS NOTEST NOREFR SYSPRINT DD SYSOUT SYSUT1 DD UNIT SYSALLDA SPACE 1024 500 20 SYSLMOD DD DSN CAI CAILIB DISP SHR SYSLIN DD DSN amp amp OBJSET DISP OLD DELETE DD INCLUDE ACF2LIB ACFGCVT ENTRY XCOMACF2 NAME 2 Sample Files 33 Sample XCDEFHLP Sample XCDEFHLP C 34 User Guide This member contains JCL to define and populate the Unicenter CA XCOM Data Transport CICS MVS HELP File JOBNAME JOB ACCOUNTING XCOMHELP DEFINE CLASS A MSGCLASS X MSGLEVEL 1 1 NOTIFY TSOID DEFHELP EXEC PGM IDCAMS SYSPRINT DD SYSOUT DD1 DD DSN XCOM CICS RVRMP XCOMHELP DISP SHR SYSIN DD 4 DELETE AND REDEFINE THE XCOMCICS HELP FILE 7 DELETE XCOM XCOMHELP VS PURGE CLUSTER DEFINE CL NAME XCOM XCOMHELP VS IXD REC 4000 1000 RECSZ 99 99 FREESPACE 0 0 KEYS 16 0 SHR 2 DATA NAME XCOM XCOMHEL
17. List Name Login User Name Indicates the remote destination where the file is to be sent Value Definition SNA destination name Specifies the SNA name of the remote system where the transfer is directed 1 to 8 characters Group name Specifies the name of a destination member defined in the Unicenter CA XCOM Data Transport Control Library This member can contain a single SNA LU name or TCP IP name or address or up to 16 SNA LU names 1 to 8 characters List name Specifies a list of SNA LU names and TCP IP addresses 1 to 8 characters Login user name Specifies a user ID on the source computer whose access privileges are used to execute the file transfer 1 to 8 characters IP destination name Specifies the IP destination name of the remote system where the transfer is directed 1 to 63 characters nnn nnn nnn nnn Specifies the IP address of the remote system where the transfer is directed Notes The contents of the Remote System Identification field reflect the choices made in the Primary Option Menu screen The first item in the field identifies one of the Unicenter CA XCOM Data Transport destination types that is the first item is one of the expressions IP Name Addr SNA LU Name XCOM Group Name XCOM List Name or Login User Name depending on what was entered as the destination type on the Primary Option Menu screen If the first item in the field is IP Name Addr another field IP Port
18. Value Definition xxxxxxxxxx Specifies up to ten alphanumeric characters indicating the unit type where the data set is to be created or where it resides for existing non cataloged data sets Default Unicenter CA XCOM Data Transport Default Options Table defaults Indicates the volume name where the data set is to be created Value Definition xxxxxxxxxx Specifies up to ten alphanumeric characters indicating the volume type where the data set is to be created or where it resides for existing non cataloged data sets Default Unicenter CA XCOM Data Transport Default Options Table defaults The Batch Interface 3 61 SYSINO1 Parameters SYSINO1 Parameters Required by FILETYPE REPORT The following additional parameters should only be coded when FILETYPE REPORT has been selected CHARS Indicates the character set JES uses when the report is sent to a remote system Value Definition Xxxx Specifies up to four alphanumeric characters representing the character set JES uses when a report is sent to a remote system Default None CLASS Specifies the print class to which the report is printed For example if the receiving system is a z OS supported mainframe indicate the JES SYSOUT class desired Value Definition x Specifies one alphanumeric character representing the print class where the report is printed Notes When sending a report to a DEC VAX computer if you specify a value for CLASS make certain that it is a
19. 000300 AUTHOR COMPUTER ASSOCIATES INTERNATIONAL 000400 000500 000600 000700 000800 DATE WRITTEN SEP 2001 000900 DATE COMPILED SEP 2001 001000 001100 ENVIRONMENT DIVISION 001200 CONFIGURATION SECTION 001300 INPUT OUTPUT SECTION 001400 FILE CONTROL 001500 SELECT SYSIN FILE ASSIGN TO S S YSIN 1 001600 001700 DATA DIVISION 001800 FILE SECTION 001900 FD SYSIN FILE Calling Unicenter CA XCOM Data Transport from a COBOL Program 002000 LABEL RECORDS ARE STANDARD 002100 RECORD CONTAINS 80 CHARACTERS 002200 BLOCK CONTAINS 0 RECORDS 002300 DATA RECORD IS SYSIN REC 002400 01 SYSIN REC PIC X 80 002500 002600 WORKING STORAGE SECTION 002700 01 XCOM API PIC X 8 VALUE XCOMJOB 002800 01 XCOM PARM 002900 05 XCOM PARM LEN PIC 59 4 COMP VALUE 44 003000 05 XCOM PARM DATA PIC X 46 003100 VALUE TYPE EXECUTE LOGMODE XCOMMODE STCAPPL XCOMAPPL 003200 003300 PROCEDURE DIVISION 003400 STARTUP SECTION 003500 003600 HERE WE CREATE SYSINO1 FILE INSTREAM 000370 III KK K KOR KOR KOR K K 003800 OPEN OUTPUT SYSIN FILE 003900 MOVE LU LU26505 TO SYSIN REC WRITE SYSIN REC 004000 MOVE COMPRESS YES TO SYSIN REC WRITE SYSIN REC 004100 MOVE TYPE SEND TO SYSIN REC WRITE SYSIN REC 004300 MOVE FILETYPE FILE TO
20. 1 Writer Name Print Class H Hold Printing Forms Control Buffer Compression Mode YES Pack Data Records NO Transfer User Data System User Data Local System Information TURKIO1 TURKIO1 11 Hold F4 RETURN F5 RFIND 6 F12 Alloc The Menu Interface TSO ISPF Panels 2 47 Send Report To Another System Screen Parameter Fields Transfer ID Execution Priority 2 48 User Guide The parameter fields of the Send Report screen are described in the following Associates a descriptive identifier with this file transfer It complements the request number assigned by Unicenter CA XCOM Data Transport to every locally initiated transfer Value Definition XXXXXXXXXX Specifies up to ten alphanumeric or national characters associating a descriptive identifier with this file transfer Notes The Unicenter CA XCOM Data Transport transfer IDs form a sequence that starts with 001 and is incremented by 1 for each transfer Default TSO user ID uuuuuuu with a sequence number nnn appended that is uuuuuuunnn Specifies the execution priority for a transfer request Value Definition 1 to 255 Specifies up to ten alphanumeric or national characters representing the execution priority for this request 1 is the lowest execution priority Notes When multiple Unicenter CA XCOM Data Transport transmissions are executing concurrently transfers with higher execution prior
21. 3 66 User Guide DEN EXPDT SYSINO1 Parameters Specifies the density to be used in creating a tape on the local or remote system Value 1to4 Definition Specifies the density to be used in creating a tape on the local or remote system Valid values are the same as those for the DEN parameter in JCL Specifies the expiration date to be placed on the tape data set being created Value yyddd yyyy ddd Definition Specifies an expiration date for the tape data set as a two digit designation for the year and a three digit designation for the day of the year For example in the expiration date 06021 06 is the year namely 2006 and 021 is the 21st day of that year The tape data set will expire on January 21 2006 Specifies an expiration date for the tape data set in terms of a four digit designation for the year and a three digit designation for the day of the year For example in the expiration date 2006 021 2006 is the year and 021 is the 21st day of that year The tape data set will expire on January 21 2006 Note EXPDT and RETPD are mutually exclusive specify one or the other The Batch Interface 3 67 SYSINO1 Parameters LABEL 3 68 User Guide Indicates the type of label associated with a tape data set The label of a tape data set is specified in terms of a sequence number and a designation for the type of processing to be applied to the data set The following table lists the valid values for b
22. CREATE XCOM TEMPORARY CSD FILE ACRE DEFCSD EXEC PGM IDCAMS INSTCSD DD DSN XCOM CICS RVRMP XCOMCSD DISP SHR SYSPRINT DD SYSOUT SYSIN DD DEFINE THE CSD CICS SYSTEM DEFINITION DEFINE CL NAME XCOM TEMP DFHCSD IXD REC 4000 RECSZ 100 500 FREESPACE 0 0 SHR 2 VOLUMES DATA NAME XCOM TEMP DFHCSD DATA UNIQUE KEYS 220 INDEX NAME XCOM TEMP DFHCSD INDEX UNIQUE REPRO IFILE INSTCSD ODS XCOM TEMP DFHCSD REPLACE OBI IOI KOR K KKR K K K A k K COPY XCOM CSD ENTRIES TO YOUR CSD FILE COPYCSD EXEC PGM DFHCSDUP COND 8 LT DEFCSD STEPLIB DD DSN YOUR CICS LOADLIB DISP SHR gt UPDATE DFHCSD DD DSN YOUR CICS CSD FILE DISP SHR gt UPDATE XCOMCSD DD DSN XCOM CICS TEMP DFHCSD DISP SHR gt UPDATE SYSPRINT DD SYSOUT SYSIN DD COPY XCOM CSD GROUP TO YOUR CSD FILE COPY GROUP XCOMGRP TO XCOMGRP REPLACE FROMCSD XCOMCSD ADD XCOMCSD GROUP TO YOUR STARTUP LIST THIS CAN BE DONE THROUGH JCL OR THROUGH THE ONLINE CEDA TRANSACTION OBO K KOR
23. Dropsess 2 52 User Guide Notes The contents of the Remote System Identification field reflect the choices made in the Primary Option Menu screen The first item in the field identifies one of the Unicenter CA XCOM Data Transport destination types that is the first item is one of the expressions IP Name Addr SNA LU Name XCOM Group Name XCOM List Name or Login User Name depending on what was entered as the destination type on the Primary Option Menu screen If the first item in the field is IP Name Addr another field IP Port appears to the right on the same line The second item in the Remote System Identification field is a specific destination name or a number in the case of an IP address You cannot change the destination type for instance SNA LU Name to XCOM Group Name but you can change the specific destination name or number Default The remote destination specified on the Primary Option Menu Specifies whether a session with a Unicenter CA XCOM Data Transport partner should be terminated at the completion of a file transfer Optional Note This field is displayed only when an SNA type of partner is referenced in the Remote System Identification field Value Definition Y Indicates that the session is to be terminated after the transfer has completed N Indicates that the session is to be retained after the transfer has completed Q Indicates that the session is to be terminated if there are no additional
24. IDS XCOM X XCOMHIST DS XCOM X XCOMIDNT AIX PATH NAME XCOM X XCOMREQ PATH P ENT XCOM X XCOMREQ AIX UPDATE PATH NAME XCOM X XCOMRECP PATH P ENT XCOM X XCOMRECP AIX UPDATE PATH NAME XCOM X XCOMUSER PATH P ENT XCOM X XCOMUSER AIX UPDATE Sample DEFQSAM Job to Define Global and Restart Data Sets Member DEFQSAM DEF PATH NAME XCOM X XCOMIDNT PATH PENT XCOM X XCOMIDNT AIX UPDATE Sample DEFQSAM Job to Define Global and Restart Data Sets Member DEFQSAM The following is a copy of the sample DEFQSAM Job found on the distribution tape CAI CINBOSAM DEFQSAM JOBNAME JOB ACCOUNTING INSTALLATION lt 1 CLASS X MSGCLASS X MSGLEVEL 1 1 I FG DOC CREATE XCOMJOB GLOBAL AND RESTART SEQUENTIAL FILES CHANGE 1 SUPPLY A VALID JOBCARD FOR YOUR INSTALLATION 2 DATASET NAME BE USED FOR YOUR GLOBAL DATASET d 3 VOLUME UPON WHICH THE GLOBAL DATASET SHOULD RESIDE 4 DATASET NAME TO BE USED FOR YOUR RESTART DATASET 77 5 VOLUME UPON WHICH THE 5 DATASET SHOULD RESIDE NOTE A SEPARATE RESTART DATA SET SHOULD BE DEFINED FOR EACH TYPE EXECUTE JOB THEY ARE NOT SHARABLE
25. N 71ename Note CA XCOM for OS 2 does not support the transfer of extended attributes The following table defines the parts of an HPFS file name for OS 2 Pari d Description A particular device The C drive is the most common local hard drive and the F drive is the most common network drive PCs also support a facility in which a section of memory RAM can be used as a virtual disk drive In high speed link environments the performance of CA XCOM is directly related to the speed of the disk drive In most environments the fastest to the slowest devices are as follows m RAM disks D drive m Directly connected hard disks C drive m Network disks F drive If you do not specify a drive the default current drive is used OS 2 Part Description directory name One or more optional directories allowing you to organize the drive Range Up to 254 characters including an optional extension like a file If you do not specify a directory the default current directory is used Note If you specify a destination file name in a directory that does not exist CA XCOM for OS 2 creates the directory for you See the target system s configuration to determine if this option has been set filename Required Restrictions The name of the data file Range 1 to 254 characters Separate components of the name with periods Note Executable binary files end with the extension EXE while executable batch files
26. SYSLIN DD DSN amp amp OBJSET DISP OLD DELETE DD ENTRY XCOMRACF NAME XCOMRACF R Sample JCL for Reassembling and Link Editing XCOMTOPS Member ASMTOPSU Sample JCL for Reassembling and Link Editing XCOMTOPS Member ASMTOPSU This member contains sample JCL for reassembling and link editing the XCOMTOPS user security exit found on the distribution tape see CALCINBOSAM ASMTOPSU Assembling the XCOMTOPS interface is optional JOBNAME JOB ACCOUNTING XCOM INSTALLATION CLASS X MSGCLASS X MSGLEVEL 1 1 FOB OIC III KOR K KOK K k KOK ARK THIS JCL ASSEMBLES THE XCOMTOPS USER SECURITY EXIT FOR UID 1 ALTER JOBCARD TO CONFORM TO INSTALLATION STANDARDS IF 2 ENSURE UID IS CODED ON SYSPARM ASSEMBLER PARM T 3 CHANGE SYSLIB TO POINT TO XCOM MACLIB 4 CHANGE SYSIN TO POINT TO XCOM CINBOSAM 5 CHANGE SYSLMOD TO POINT TO XCOM LOAD LIBRARY Jf n CHANGE HISTORY ID DATE DESCRIPTION N A 06 21 02 CREATION RRR KR KK OK KK KK KK KKK ASMTOPS EXEC 5 90 PARM SYSPARM UID OBJECT NODECK XREF SHORT NORENT SYSLIB DD DSN XCOM RVRMP MACLIB DISP SHR DD DSN SYS1 MACLIB DISP SHR DD DSN SYS1 AMODGEN DISP SHR DD DSN SYS1 MODGEN DISP SHR S
27. Send Report To Another System Screen Compression Mode 2 58 User Guide Specifies whether or not Unicenter CA XCOM Data Transport compresses the data being transferred and decompresses it on the remote system Compressing the data decreases the transmission time on lower speed links Value Definition YES Provides Run Length Encoding RLE for blanks and binary zeros only NO No data compression RLE Provides complete Run Length Encoding for all characters COMPACT Provides full RLE as in RLE above plus a byte compaction scheme that is suitable for uppercase English text COMPACTL Same as COMPACT above only the compaction scheme is most beneficial for lowercase English text LZSMALL Lempel Ziv 77 compression with a small memory allocation scheme LZMEDIUM Lempel Ziv 77 compression with a medium memory allocation scheme LZLARGE Lempel Ziv 77 compression with a large memory allocation scheme HUFFMAN Greater compression than RLE but not as much as the Lempel Ziv 77 modes LZRW3 General purpose algorithm that runs fast and gives reasonable compression ZLIB n Greater compression than LZRW3 but less than LZSMALL LZMEDIUM and LZLARGE The n value can be 1 through 9 Default YES Pack Data Records Send Report To Another System Screen Specifies whether record packing is to be used on a file transfer Value Definition NO Specifies that no record packing is used The data are sent unblocked LENGTH Spec
28. TYPE 3 26 User Guide Specifies how Unicenter CA XCOM Data Transport is to process the transfer request Required Value SCHEDULE Definition Queues the file transfer request and ends the job step when the transfer request is queued The request runs in the address space of the Unicenter CA XCOM Data Transport server The file transfer is single threaded in first in first out queuing order unless overridden by priority considerations and is implemented when the resource becomes available If the target computer is unavailable during the execution of a job the transfer occurs as soon as it becomes available If the target computer is available and the Unicenter CA XCOM Data Transport server is active the transfer may be executed immediately TYPE SCHEDULE is recommended for production jobs EXECUTE INQUIRE Notes Indicates that the file transfer is to be processed during the execution of the current job If the file transfer cannot be executed before the specified job time out interval Unicenter CA XCOM Data Transport generates condition codes and messages This transfer type is supported by most Unicenter CA XCOM Data Transport platforms For a list of restrictions call Unicenter CA XCOM Data Transport Customer Support If TYPE EXECUTE and another user has established a session with the same target computer your job aborts if the other user s session does not end before the time out interval has expired
29. VAX 9 8 APPC A 5 VERSION MODIFY command 6 48 VM 9 18 VOL SYSINO1 parameter 3 61 system parameter 6 17 VOLCT SYSINO1 parameter 3 71 VOLSQ SYSINO1 parameter 3 71 volume allocate new serial 2 43 Receive File From Another System screen 2 95 2 98 Send File screen 2 33 2 36 VPSPRINT TSO command 5 1 VSAM files ESDS 7 6 KSDS 7 6 RRDS 7 6 history file purge utility B 2 JCL VSAM request queue C 1 VSE 9 20 VTAM APPLID definition table C 10 compression bytes Detailed File Transfer screen 2 121 VTAMGNAM PARM parameter 3 27 VTOC read by Unicenter CA XCOM Data Transport 7 1 W wandering LU 2 8 wildcards 7 2 Windows 9 26 Windows NT 9 28 Index 16 User Guide WRITER destination table parameter 5 8 SYSINO1 parameter 3 66 writer name Send Report screen 2 56 WTO macro Send Report screen 2 62 Submit Job screen 2 77 X XCDEFHLP sample JCL C 34 XCOM group name 2 7 XCOM list name 2 8 XCOM Operator Control Selection menu option 2 5 CONFIG SSL SYSINO1 parameter 3 55 XCOMACE sample JCL C 30 user security exit sample C 33 XCOMADM sample JCL C 20 XCOMADMT sample table C 17 XCOMCNTL data set name Selection menu 2 11 XCOMDELT sample macro 15 user exit calling module D 8 XCOMDSPL user exit calling module D 8 XCOMENCR sample JCL C 36 encrypt SYSINO1 LPASS C 36 encrypt SYSINO1 PASSWORD C 36
30. Value YES NO Definition Tells Unicenter CA XCOM Data Transport to use OpenSSL for the transfer of the file and that it must connect to an SSL port on the remote partner Tells Unicenter CA XCOM Data Transport that the file does not require a secure connection and should be handled as a regular file transfer Specifies whether Unicenter CA XCOM Data Transport adds a record separator to delimit logical records Note Skip this field unless you are sending data to an ASCII computer Value Y N Default N Definition Unicenter CA XCOM Data Transport adds a record separator such as a line feed and carriage return to delimit logical records Unicenter CA XCOM Data Transport does not add record separators The Menu Interface TSO ISPF Panels 2 71 Submit Job To Another System Screen EBCDIC Binary ASCII Truncate Record 2 72 User Guide Indicates the type of transferred data The receiving computer is responsible for performing any necessary conversion Value Definition B Indicates binary data E Indicates that the data is in EBCDIC code A Indicates that the data is in ASCII code Default E Notes EBCDIC packed decimal fields cannot be transferred under EBCDIC Use BINARY to transfer EBCDIC packed decimal data Specifies how records exceeding the maximum logical record length LRECL are to be handled Value Definition Y Specifies that records larger than the maximum LRECL are to be tr
31. oldpassword newpas sword Domain Notify User Send MVS File To Another System Screen Identifies the Windows 2000 2003 or XP domain associated with the remote server Value Definition Up to 15 Specifies up to 15 alphanumeric characters representing the alphanumeric domain user password and ID associated with the remote characters server Notes Can only be used for transfers running under Windows 2000 2003 or Identifies the user on the remote system Unicenter CA XCOM Data Transport is to notify once the transfer completes Value Definition LOG LOG requests that the main operator on the remote computer be notified If the remote computer is a z OS system a WTO macro is issued by Unicenter CA XCOM Data Transport On an AS 400 or VAX system the operator console is notified user_id If any value but LOG is given Unicenter CA XCOM Data Transport interprets this as a specific user ID on the remote system If that user is not logged on when the transfer completes the message is displayed the next time the user logs on Default LOG The Menu Interface TSO ISPF Panels 2 33 Send MVS File To Another System Screen Volume Unit 2 34 User Guide Indicates the volume on the remote system on which the file is to be created or resides for existing non cataloged files Value Definition XXXXXXXXXX Specifies the volume on the remote system on which the file is to be created or resides for existin
32. A VTAM error occurred TYPE EXECUTE 20 TYPE SCHEDULE 32 Another type of error occurred for TYPE EXECUTE example an incorrectly coded TYPE SCHEDULE parameter 36 At least one transfer request exists TYPE INQUIRE for which status information is not yet available 40 At least one transfer did not TYPE INQUIRE complete successfully 44 There is at least one transfer request TYPE INQUIRE for which status information is not yet available and at least one transfer request that did not complete successfully 48 No history record was found for the TYPE INQUIRE request The Batch Interface 3 83 Chapter 4 The Programming Interface This chapter describes how to invoke Unicenter CA XCOM Data Transport from application programs to execute file transfers Examples of COBOL and Assembler main programs calling XCOMJOB as a subprogram have also been provided Any programming language supporting standard z OS linkage conventions can call Unicenter CA XCOM Data Transport including the following m COBOL m FORTRAN m Assembler The Programming Interface 4 1 The Unicenter CA XCOM Data Transport Process The Unicenter CA XCOM Data Transport Process 4 2 User Guide Unicenter CA XCOM Data Transport can be directed to execute a file transfer immediately or to queue it until the necessary resources are available These instructions and all the transfer s processing options are given to Unicenter CA XCOM Data Tran
33. E or ENGLISH The control information does not contain Katakana characters Note JPNCNTL is valid for CODE EBCDIC transfers only Default E ENGLISH JPNDATA JPNDBL JPNSHFT SYSINO1 Parameters Indicates whether the data file contains Katakana characters Value Definition Kor KATAKANA The data file being transferred contains Katakana characters E or ENGLISH The data file does not contain Katakana characters Note JPNDATA is valid for CODE EBCDIC transfers only Default E ENGLISH Indicates the local double byte character set for Japanese conversions Value Definition 0 IBM double byte character set Note This parameter is no longer supported only IBM DBCS is supported Specifies whether DBCS shift out and shift in characters are removed or converted to spaces Value Definition CorCONVERT DBCS shift out shift in characters are converted to spaces D or DELETE The DBCS shift out shift in characters are removed Note JPNSHFT is valid for CODE EBCDIC transfers only Default D DELETE The Batch Interface 3 41 SYSINO1 Parameters LFILE Identifies the local data set involved in a file transfer Value Definition 1 to 54 Specifies the local data set involved in a file transfer This can characters be the name of a file copied to a remote system or the filename of a data set received from a remote system Alternatively the local data set name can be specified using the
34. Fixed ASA Fixed Blocked Fixed Blocked ASA Fixed Blocked Machine Fixed Blocked Standard Variable Variable ASA Variable Blocked Record Length Block Size Data Class File Allocation Information Screen Value Definition VBA Variable Blocked ASA VBM Variable Blocked Machine VBS Variable Blocked Spanned VS Variable Spanned U Undefined Value Definition Up to seven numeric Defines the logical record length of the file characters Value Definition Up to six numeric Defines the block size of the file characters Specifies the name of the data class to use when allocating a new SMS managed data set Value XXXXXXXX Definition Specifies the 1 to 8 character data class name to use when allocating a new SMS managed data set Note This parameter applies only to mainframe SMS data sets Default None The Menu Interface TSO ISPF Panels 2 45 File Allocation Information Screen Management Class Storage Class 2 46 User Guide Specifies the name of the management class to use when allocating a new SMS managed data set Value Definition xxxxxxxx Specifies the 1 to 8 character management class name to use when allocating a new SMS managed data set Note This parameter applies only to mainframe SMS data sets Default None Specifies the name of the storage class for a new SMS managed data set Value Definition xxxxxxxx Specifies the 1 to 8 character storage class name to use when
35. Indicates that the transfer should be sent to the specified user Note The login user name is identified by the Unicenter CA XCOM Data Transport wandering LU or CheckIn CheckOut feature Only a single user system PC DOS Windows OS 2 can be the partner for this type of transfer Value Definition xxxxxxxx Specifies up to eight alphanumeric and national characters representing a user whose session will be used for the transfer The initial character must be national or alphabetic Notes This parameter is mutually exclusive with XCOM Group Name Login User Name SNA LU Name IP Name and XCOM List Name one of the five must be specified for each file transfer request If a security environment exists the user names must be defined to the security environment for Unicenter CA XCOM Data Transport This parameter is valid only for queued transfers The Unicenter CA XCOM Data Transport Transfer Request Display screen can be used to check on the current completion status of any transfer The Menu Interface TSO ISPF Panels 2 9 The Primary Option Menu Queue for Execution 2 10 User Guide Specifies whether this transfer request should be queued for execution by the Unicenter CA XCOM Data Transport server or through the XCOMPLEX Admin Server or executed immediately Value Y Default Y Definition This request will be queued for execution by the Unicenter CA XCOM Data Transport server or the XCOMPLEX Admin Server
36. Indicates whether all transfers specified in a job request have completed successfully and whether any transfers were incomplete or unsuccessful For more information about return codes see XCOMJOB Return Codes in this chapter VTAMGNAM XCOMPLEX PARM Parameters Specifies the VTAM Generic Resource Name that the server attempts to open at initialization time Note This parameter is valid only for the Unicenter CA XCOM Data Transport server job Value Definition XXXXXXXx Specify the 1 to 8 character alphanumeric Generic Resource Name Default None Specifies the name of the XCOMPLEX facility that the Unicenter CA XCOM Data Transport Administrator administers Specify the same XCOMPLEX name for each Unicenter CA XCOM Data Transport server that is a member of the XCOMPLEX facility The name for the XCOMPLEX must be unique and may not be the same as the acbname for any server in the XCOMPLEX Note This parameter is valid for the Unicenter CA XCOM Data Transport server job and the Unicenter CA XCOM Data Transport administrator job Value Definition XXXxxxxxxxxxxxxx Specify the 1 to 16 character alphanumeric name of the XCOMPLEX to join Default None The Batch Interface 3 27 SYSINO1 Parameters SYSINO1 Parameters This section describes the set of parameters that are specified the SYSINO1 DD statement of the XCOMJOB JCL The discussion of the SYSINO1 parameters is divided into the following su
37. LOADLIB DD DISP SHR DSN CEE SCEERUN IBM C RUNTIME SYSTCPD DD DSN TCPIP TCPIP DATA DISP SHR IBM TCP IP XCOMCNTL DD DSN XCOM RBO XCOMCNTL DISP SHR SYSPRINT DD SYSOUT SYSINO1 DD TYPE SEND DROPSESS YES NEWXFER TYPE SEND C 26 User Guide Sample XCOMJOB Inquire JCL Member XCOMJOBI Sample XCOMJOB Inquire JCL Member XCOMJOBI This member contains a sample XCOMJOB Inquire JCL found on the distribution tape CAI CINBOSAM XCOMJCODBI This illustrates JCL for a TYPE INQUIRE transfer XCOMWAIT JOB XCOM 0028 name CLASS A MSGCLASS X THIS STEP USES XCOMJOB TYPE SCHEDULE TO INITIATE A FILE TRANSFER BECAUSE THE XCOMINQ DD CARD IS INCLUDED XCOMJOB SAVES THE REQUEST NUMBER ASSIGNED TO THE TRANSFER IN THE XCOMINQ FILE STEPO1 EXEC PGM XCOMJOB PARM TYPE SCHEDULE 1 CONTINUE NO STCAPPL XCOMAPPL XCOMCNTL DD DISP SHR DSN XCOM RBO XCOMCNTL XCOMINQ DD DISP SHR DSN XCOM RBO XCOMINQ SYSINO DD TYPE SEND LU XCOMMJM2 FILETYPE FILE FILEOPT REPLACE LFILE XCOM28 FILE1 FILE XCOM28 FILE2 THIS STEP USES XCOMJOB TYPE SCHEDULE TO INITIATE A FILE TRANSFER SINCE THE SAME XCOMINQ FILE IS USED AS IN THE PREVIOUS STEP THE XCOMINQ FILE WILL CONTAIN BOTH REQUEST NUMBERS STEPO2 EXEC PGM XCOMJOB PARM TYPE SCHEDULE ACBNAME XCOMM1 CONTINUE NO STCAPPL XCOMAPPL XCOMCNTL DD DISP SHR DSN XCOM RB
38. List name Specifies a list of SNA LU names and or TCP IP addresses 1 to 8 characters Login user name Specifies a user ID on the source computer whose access privileges are used to execute the file transfer 1 to 8 characters IP destination name Specifies the IP destination name of the remote system where the transfer is directed 1 to 63 characters nnn nnn nnn nnn Specifies the IP address of the remote system where the transfer is directed Notes The contents of the Remote System Identification field reflect the choices made in the Primary Option Menu screen The first item in the field identifies one of the Unicenter CA XCOM Data Transport destination types that is the first item is one of the expressions IP Name Addr SNA LU Name XCOM Group Name XCOM List Name or Login User Name depending on what was entered as the destination type on the Primary Option Menu screen If the first item in the field is IP Name Addr another field IP Port appears to the right on the same line The second item in the Remote System Identification field is a specific destination name or a number in the case of an IP address You cannot change the destination type for instance SNA LU Name to XCOM Group Name but you can change the specific destination name or number Default The remote destination specified on the Primary Option Menu The Menu Interface TSO ISPF Panels 2 69 Submit Job To Another System Screen DROPSESS
39. Non queued host transfers Due to restrictions in the DEC SNA software the z OS TYPE EXECUTE non queued transfer feature fails with an 8003 sense code It is not supported by Unicenter CA XCOM Data Transport to an OpenVMS system Operating system Unicenter CA XCOM Data Transport currently supports the OpenVMS Alpha and OpenVMS VAX operating systems The Unicenter CA XCOM Data Transport guides frequently abbreviate the name of this operating system as VAX This is not meant to imply support for UNIX Connectivity The DECNET SNA software is based on the Physical Unit 2 0 standard and not on the more flexible 2 1 This means that the system must be connected to a VTAM PU 5 system in an SNA network Unicenter CA XCOM Data Transport uses the store and forward function described previously as an additional z OS VM and VSE feature to transfer files with other Unicenter CA XCOM Data Transport partners Multiple session configuration Digital does not support parallel sessions with a z OS system However if three file transfers are needed concurrently with an OpenVMS system it does allow you to define three APPC logical units as a group group name can be from one to eight characters The first character must be alphabetic while the rest can be any combination of alphanumeric or national characters Try to use mnemonic names This feature is useful for assigning nicknames as well The following example calls three logical un
40. Port 2 70 User Guide Indicates whether Unicenter CA XCOM Data Transport drops an LU to LU session at the conclusion of a scheduled file transfer Value Definition YES Indicates that Unicenter CA XCOM Data Transport drops the session NO Indicates that Unicenter CA XCOM Data Transport does not drop the session Indicates that Unicenter CA XCOM Data Transport is to process all the transfers to a particular LU in the request queue before dropping the session Default NO Notes Unicenter CA XCOM Data Transport for VAX and some Unicenter CA XCOM Data Transport for UNIX products do not support z OS initiated session establishment Therefore DROPSESS has no effect when the target of the transfer request is one of these platforms Specifies the number of the IP port where Unicenter CA XCOM Data Transport listens at the remote system Note This field is displayed on the screen only when an IP name or address is referenced in the Remote System Identification field Value Definition 1 to 65535 Identifies the IP port monitored listened to by Unicenter CA XCOM Data Transport at the remote system Notes If this field is left blank the port value specified in the Unicenter CA XCOM Data Transport Default Options Table is used Secure Socket SSL Record Separators Submit Job To Another System Screen Informs Unicenter CA XCOM Data Transport how to handle the security of the transfer to the remote system
41. SYSOUT advantages of the interface 5 1 class 6 16 diagnostic dumps 6 16 external writer 5 8 JES spool files 5 2 use with TSO 5 7 with CICS 5 6 with other online systems 5 6 Index 13 SYSPLEX define XCOMPLEX C 18 SYSPRINT DD statement 3 6 B 5 SYSTCPD DD statement 3 6 system administrator table sample C 17 System Management Facility See SMF system name Selection menu 2 7 system parameter IPPORT 3 17 SYSTERM DD statement 3 6 SYSUDATA 5 01 parameter 2 29 2 60 2 75 2 92 3 53 Tandem 9 14 tape parameters See also SYSINO1 parameters DEN 3 67 EXPDT 3 67 LABEL 3 68 LLABEL 3 69 LUNITC 3 70 LVOLCT 3 70 LVOLSO 3 70 RETPD 3 70 TAPE 3 71 UNIICT 3 71 VOLCT 3 71 VOLSQ 3 71 TAPE SYSINO1 parameter 3 71 TCP IP node addressing 1 10 protocol stack outline 1 8 remote system identification 2 6 transfers 3 15 3 17 3 37 TCPSESS system parameter 6 17 TCPSTACK PARM parameter 3 24 TDUDATA SYSIN01 parameter 3 53 temporary data sets 6 17 TERM MODIFY command 6 45 termination processing user exit D 17 TERMTD status field 2 119 third party processing 3 2 Index 14 User Guide TIME attribute label 2 116 TIMEOUT PARM parameter 3 16 3 25 total bytes transferred Detailed File Transfer screen 2 121 TPF transactions 5 2 trace deactivation parameters 6 30 parameters 6 47 TRACE MODIFY command 6 47 PARM parameter 3 26 transaction CICS
42. The two parts can be a maximum of eight characters in length They can consist of letters numbers and or national characters In general lowercase letters are not allowed In the Unicenter CA XCOM Data Transport for VM parameters FILE and LFILE the file name and file type are specified as one string with a period as a separator For minidisk specifications a CP OWNER is taken from the volume field if present Otherwise the userid field is used m CP address is taken from the unit specification The default is 191 Note You may have two files with the same file name and file type but they cannot reside on the same minidisk VM Types of Files Supported DCB Information Restriction The Unicenter CA XCOM Data Transport Service Virtual Machine runs IBM s GCS Group Control System operating system Due to the limitations of this environment Unicenter CA XCOM Data Transport for VM only supports the CMS extended file system format This covers CMS files on minidisks formatted with 512 1 024K 2 048K and 4 096K block sizes Note It does not support the following CMS Shared File System minidisks formatted with 800 byte blocks or tape I O CMS file characteristics must be predetermined when creating a new file You must specify the following parameters m Record format This can be fixed F or variable V Logical record length This is the number of characters in the longest line of the
43. The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level READ 6 32 User Guide Resource Name XCOM applsec NSASTAT The applsec variable represents the value of the APPLSEC parameter in the Default Options Table Using the Unicenter CA XCOM Data Transport MODIFY Commands RELEASE Command Releases a held file transfer Format F XCOM RELEASE nnnnnn Operands The following operand is used with the RELEASE command Operand Description nnnnnn Specifies the request number 0 to 999999 of the transfer to be released Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec RELEASE destname ownername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination involved in the transfer m ownername the user ID under whose security authorization the transfer is performed Operation and Control 6 33 Using the Unicenter CA XCOM Data Transport MODIFY Commands RESET Command Format Operands Notes 6 34 User Guide Immediately resets any error flags F XCOM RESet des name The fo
44. Unicenter CA XCOM Data Transport processes relative record data sets sequentially without preserving relative record numbers across systems Source RRDS records are written into the target RRDS data set sequentially starting with relative key 1 You must also employ the CREATE option if the data set has been defined with the REUSE option and is to be reused Note When creating a VSAM file make sure that the file is pre allocated on the destination system 7 6 User Guide Miscellaneous File Considerations Miscellaneous File Considerations The following are special considerations involving a variety of file types m Writing fixed length records to variable length records m Multivolume data sets m Spanned records Fixed to Variable Length Record Transfers When sending a file of fixed length records to a z OS data set of variable length records be sure that the record length of the target file is at least 4 bytes longer than that of the source file This accommodates the four byte prefix z OS systems use to define variable length records 5 400 systems do not support variable length records Instead they create target files whose fixed record length is the same as the largest variable length record of the source file This can waste considerable disk space Multivolume Data sets Spanned Records Unicenter CA XCOM Data Transport supports multivolume data sets that is files residing on more than one disk pack However ISPF
45. XCOM1K LOGMODE XCOMIK FMPROF X 13 TSPROF X 07 PRIPROT X BO SECPROT X BO COMPROT X 50B1 RUSIZES X 8787 PSNDPAC 5 SRCVPAC 5 SSNDPAC 5 LOGON MODE TABLE ENTRY NAME FUNCTION MANAGER PROFILE TRANSMISSION SERVICES PROFILE PRIMARY LOGICAL UNIT PROTOCOL SECONDARY LOGICAL UNIT PROTOCOL COMMON LOGICAL UNIT PROTOCOL RUSIZE SEC PRI 1024 1024 PRIMARY SEND PACING COUNT SECONDARY RECEIVE PACING COUNT SECONDARY SEND PACING COUNT PSERVIC X 060200000000000000002C00 PRESENTATION SRVCS XCOM1920 MODEENT LOGMODE XCOM1920 FMPROF X 13 TSPROF X 07 PRIPROT X BO SECPROT X BO COMPROT X 50B1 RUSIZES X F7F7 PSNDPAC 5 SRCVPAC 5 SSNDPAC 5 LOGON MODE TABLE ENTRY NAME FUNCTION MANAGER PROFILE TRANSMISSION SERVICES PROFILE PRIMARY LOGICAL UNIT PROTOCOL SECONDARY LOGICAL UNIT PROTOCOL COMMON LOGICAL UNIT PROTOCOL RUSIZE SEC PRI 1920 1920 PRIMARY SEND PACING COUNT SECONDARY RECEIVE PACING COUNT SECONDARY SEND PACING COUNT PSERVIC X 060200000000000000002C00 PRESENTATION SRVCS Sample Files gt X gt lt X x x gt lt gt x gt x gt lt gt lt X gt x x x gt lt gt x gt x gt gt lt gt lt X gt x x x gt lt gt x gt x gt gt x gt lt gt lt gt x x x x gt x gt x gt x lt gt lt X gt x gt x x gt lt gt x gt x gt C 13 Sample XCOMTABL Table Member XCOMTABL C 14 User Guide XCOM2K MODEENT LOGMODE XCOM2K FMPROF X 13
46. you can use the DEFINE ALIAS command to establish the PSOPREF high level qualifier as an alias for that user catalog Unicenter CA XCOM Data Transport s PSO data sets are then be cataloged in the user catalog For example assume that the user catalog CATALOG XCOM has been created for the Unicenter CA XCOM Data Transport PSO data sets To establish the high level qualifier XCOMPSO as an alias for that user catalog use the following DEFINE ALIAS command DEFINE ALIAS NAME XCOMPSO RELATE CATALOG XCOM The Remote Spooling Feature Process S YSOUT 5 13 Chapter 6 Operation and Control This chapter describes the console commands provided with the Unicenter CA XCOM Data Transport for z OS software Starting the Unicenter CA XCOM Data Transport Server To start Unicenter CA XCOM Data Transport enter one of the following commands on the z OS console or any TSO ISPF or NETVIEW session where the user is authorized to invoke z OS system commands START XCOM S XCOM Several informational messages are displayed when Unicenter CA XCOM Data Transport is started see the following example 06721 UNICENTER R CA XCOM R DATA TRANSPORT r11 GENERATION LEVEL 0410 5 00 00041 START STARTBO 00041 DFTLAB XCLSDFBO 00041 5 00081 XCOMLS ACB OPENED SUCCESSFULLY 00091 COMPILED UNDER VTAM V6 R1 M2 EXECUTING UNDER VTAM V6 R1 M2 5695 117 X
47. 05105 refers to the 105th day of year 2005 Unless you have compelling reasons for not doing so give short file transfers a higher execution priority than very large transmissions Doing so generally enhances processing efficiency The execution priority can be changed during the transmission Command Security Requirements 6 10 User Guide The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec DATE destname ownername XCOM applsec EPRTY destname ownername XCOM applsec SPRTY destname ownername XCOM applsec TIME destname ownername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination involved in the transfer m ownername the user ID under whose security authorization the transfer is performed CANCEL Command Format Operands Using the Unicenter CA XCOM Data Transport MODIFY Commands Cancels an active session F XCOM CANCEL des tname Immed Purge SUSPend The following operands are used with the CANCEL command Operand asterisk destname IMMED PURGE SUSPEND Description Cancels all active sessions Cancels the specific session associated with the designated Unicenter CA XCOM Data Transport partner destination
48. 4 LU 6 2 Independent Implementations 2 A 5 Direct Sessions with a Dependent Logical Unit A 5 PW Eat eia uaa ad EEC EEEE EEREN ie A 5 Appendix B History and SMF Files SMF Record and History 27 2 2 2 24 B 1 When Records Are Written 5 ore Si eei nee Bader shacha pash ase oes B 1 Transfers that Produce Records B 1 Transfers That Do Not Produce Records 2 B 2 Record Location iive ere m RR 2 ACOMUTIE History File Purge Utility edo esae oae vos ea UOS 2 XCOMUTTE Paratuetets 2 P3 d Pb iR TR PP P bei B 3 XCOMUTIE DD Statements 22240004044 avete a qu Re Wad ER NARRANT RN uA a RA VIV NS e dd B 5 Sample of Required 2 2 2 22 B 5 Return CodeS 6 Sample History File Purge Procedure 11 6 User Guide Appendix C Sample Files Sample JCL VSAM Request Queue Member DEFRRDS 1 Sample History File Creation JCL Member DEFHIST C 3 Sample XCOMUTIL Job
49. B and C need to be transferred to a PC destination where they are to be stored in the remote files CN A DAT C B DAT and C C DAT and that the at sign 8 is used as the remote file substitution character To accomplish this task you need to specify XCOM PDS in the Local File Name field in the Remote File Substitution Character field and C DAT as the file name schema in the Remote File Name field Once the XCOM PDS members to be transferred have been selected from the member list Unicenter CA XCOM Data Transport generates the following transfer requests Local File Name Remote File Name Schema Remote File Name and Substitution Character XCOM PDS A XCOM PDS B m XCOM PDS C Program Library Send MVS File To Another System Screen In the following example the schema for generating remote file names is based on a partitioned data set Local File Name Remote File Name Schema Remote File Name and Substitution Character XCOM PDS A XCOM PDS OUT A XCOM PDS B gt XCOM PDS OUT gt XCOM PDS OUT B XCOM PDS C XCOM PDS OUT C Note If the remote file name schema contains multiple occurrences of the Remote File Substitution Character only the first occurrence of the Substitution Character is used in the generation of Remote File Names Informs Unicenter CA XCOM Data Transport how to handle the file that is being transferred to the remote
50. Maximum Entries Limits the number of file transfers displayed for a particular server or for each XCOMPLEX Worker Server when the APPLID is of an XCOMPLEX Admin Server Value Definition Up to four numeric characters Specifies the maximum number of transfers for a certain server or for each XCOMPLEX Worker Server when the APPLID is of an XCOMPLEX Admin Server Unicenter CA XCOM Data Transport Transfer Request Display Screen The XCOM Transfer Request Display screen provides information on the set of file transfers defined on the File Transfer Display Select screen CA XCOM Transfer Request Display ROW 1 OF 8 COMMAND INPUT gt SCROLL gt PAGE CA XCOM Server XCSDSDL Req Trans Prty Where Start Type Xfer ID SL EX User ID Started Date Time Status 001009 SENDFIL DA1SZ95I 16 16 DA1SZ95 LOCAL 20040828 1414 COMPLT Remote System LU30107 2 112 User Guide LOCL FI REMT FI 001010 SEND Remote Syste LOCL FI REMT FI LE DA1SZ95 XCOM R223 SAMPLIB GINDEX LE C XCOMDATA INDEX SAM FIL DA1SZ95I 1616 DA1SZ95 LOCAL m LU30107 LE DA1SZ95 XCOM R223 SAMPLIB APPLXCOM LE C XCOMDATA APPLXCOM SAM 001011 SENDFIL DA1SZ95I 16 16 DA1SZ95 LOCAL Remote Syste LOCL FI REMT FI m LU30107 LE DA1SZ95 XCOM R223 SAMPLIB ASM TBLS LE C XCOMATA ASM TBLS SAM 001012 SENDFIL DA1SZ95I 16 16 DA1SZ95 LOCAL Remote Syste LOCL FI REMT FI 001013 SENDI Remote Syste LOCL FI REMT FI F1 Help F F7 UP F m LU30107 LE D
51. Member 2 2 4 2 2 C 6 Sample DEFOSAM Job to Define Global and Restart Data Sets Member DEFQSAM C 9 Sample JCL for Defining the Inquire Data Set Member DEFINQ C 10 Sample VTAM APPLID Definition Table Member C 10 Sample XCOMTABL Table Member C 12 Sample XCOMDFLT Macro Member C 15 Sample XCOMADMT Table Member XCOMADMT C 17 Sample XCPF Member 2 42 2 C 18 Sample POLCFRM Member POLCFRM 242 C 19 Sample XCOMPLEX Admin 2 C 20 Sample Unicenter CA XCOM Data Transport Server JCL Member XCOM C 21 Sample XCOMESR ERI 24444246 C 22 Sample CICS Notification Transaction Member C 23 Sample XCOMJOB Execute JCL Member XCOMJOBE 24 Sample XCOMJOB Schedule JCL Member XCOMJOBS C 25 Sample XCOMJOB Schedule JCL through the X
52. REPORTHOLD SYSINOI parameter 3 66 REQNUM attribute label 2 116 request queue C 1 Index 10 User Guide requesting user ID operator control parameter 2 111 reset error flags parameters 6 34 RESET MODIFY command 6 34 restart data set defining C 9 RESTART SYSINO1 parameter 3 49 RESUME MODIFY command 6 35 resumption of failed transfers 3 11 RETPD SYSINO1 parameter 3 70 return codes 3 82 RF attribute label 2 116 RFILE attribute label 2 116 RJE 5 2 RJPWS JES2 destination statement 5 10 RLE See run length encoding RNOTIFY SYSINO1 parameter 3 49 RNOTIFYNAME SYSINO1 parameter 3 50 Roscoe transactions 5 2 routing to a specific printer 5 9 RRDS 7 6 file sample JCL C 1 RSHOW MODIFY command 6 36 run length encoding 3 10 samples application definition table C 10 APPLID C 10 CICS notification transaction C 23 COPYCSD C 37 creating a history file C 3 creating a transfer queue C 1 creating sequential data sets for non queued transfers C 9 C 10 creating XCOMGLOB and XCOMREST data sets C 9 C 10 default options table C 15 default options table parameters C 15 DEFDFLT C 35 determining transfer request status C 27 direct transfer JCL C 24 JCL for defining an XCOMPLEX Admin Server C 20 JCL for defining an XCOMPLEX structure C 19 JCL for defining an XCOMPLEX to the Coupling Facility C 18 JCL for reassembling and linkediting Unicenter CA XCOM Data Transport eTrust CA A
53. SYSINO1 parameter 3 41 Index 5 JPNDBL SYSIN01 parameter 3 41 JPNSHFT SYSINO1 parameter 3 41 K Katakana characters in file 2 100 key sequenced data set 7 6 KSDS 7 6 label type Submit Job screen 2 68 LABEL SYSINO1 parameter 3 68 last action Detailed File Transfer screen 2 121 message Detailed File Transfer screen 2 121 ms Detailed File Transfer screen 2 121 LCLDS01 allocating 4 2 DD statement 3 5 SYSINO1 parameter 3 5 3 42 LIBNEG destination parameter 7 3 system parameter 7 3 library 6 23 CLIST 2 2 transfers 7 3 LIST MODIFY command 6 28 PARM parameter 3 19 SYSINOI parameter 3 42 list name Selection menu 2 8 LLABEL SYSINO1 parameter 3 69 LOAD macro 4 5 local file name Receive File From Another System screen 2 82 Send File screen 2 17 Send Report screen 2 49 Submit Job screen 2 67 Index 6 User Guide transfers display with command line 6 38 6 51 volume Receive File From Another System screen 2 98 Send File screen 2 36 locally initiated transfer requests queue purging interval 6 16 LOCATE menu command 2 115 LOCFER status field 2 118 LOCFILE attribute label 2 116 LOG PARM parameter 3 19 system parameter 6 17 log file free the file for printing 6 29 LOGAPPL VTAM parameter A 5 LOGCER status field 2 119 LOGCL system parameter 6 17 LOGCLASS PARM parameter 3 20 LOGDEST PARM parameter 3 20 system parameter 6 17
54. Specifies the type of processing to be done on the tape data set Note Leave the field blank for disk files Value Definition SL Specifies the tape processing type SL NL Specifies the tape processing type NL NSL Specifies the tape processing type NSL SUL Specifies the tape processing type SUL BLP Specifies the tape processing type BLP LTM Specifies the tape processing type LTM AL Specifies the tape processing type AL AUL Specifies the tape processing type AUL Specifies the number of tape units to be allocated on the system Note Leave the field blank for disk files Value Definition 1 to 20 Specifies the number of the units to be allocated on the system Specifies the sequence number of the first volume of a multivolume tape data set to be used Note Leave the field blank for disk files Value Definition 1 to 255 Specifies the sequence number of the first volume of a multivolume data set to be used Submit Job To Another System Screen Remote System Identification Indicates the remote destination where the file is to be sent Value Definition SNA destination name Specifies the SNA name of the remote system where the transfer is directed 1 to 8 characters Group name Specifies the name of a destination member defined in the Unicenter CA XCOM Data Transport Control Library This member can contain a single SNA LU name or TCP IP name or address or up to 16 SNA LU names 1 to 8 characters
55. TSPROF X 07 PRIPROT X BO SECPROT X BO COMPROT X 50B1 RUSIZES X 8888 PSNDPAC 5 SRCVPAC 5 SSNDPAC 5 LOGON MODE TABLE ENTRY NAME FUNCTION MANAGER PROFILE TRANSMISSION SERVICES PROFILE PRIMARY LOGICAL UNIT PROTOCOL SECONDARY LOGICAL UNIT PROTOCOL COMMON LOGICAL UNIT PROTOCOL RUSIZE SEC PRI 2048 2048 PRIMARY SEND PACING COUNT SECONDARY RECEIVE PACING COUNT SECONDARY SEND PACING COUNT PSERVIC X 060200000000000000002C00 PRESENTATION SRVCS XCOMAK LOGMODE XCOMAK FMPROF X 13 TSPROF X 07 PRIPROT X BO SECPROT X BO COMPROT X 50B1 RUSIZES X 8989 PSNDPAC 5 SRCVPAC 5 SSNDPAC 5 LOGON MODE TABLE ENTRY NAME FUNCTION MANAGER PROFILE TRANSMISSION SERVICES PROFILE PRIMARY LOGICAL UNIT PROTOCOL SECONDARY LOGICAL UNIT PROTOCOL COMMON LOGICAL UNIT PROTOCOL RUSIZE SEC PRI 4096 4096 PRIMARY SEND PACING COUNT SECONDARY RECEIVE PACING COUNT SECONDARY SEND PACING COUNT PSERVIC X 060200000000000000002C00 PRESENTATION SRVCS XCOM8K MODEENT LOGMODE XCOM8K FMPROF X 13 TSPROF X 07 PRIPROT X BO SECPROT X BO COMPROT X 50B1 RUSIZES X 8A8A PSNDPAC 5 SRCVPAC 5 SSNDPAC 5 LOGON MODE TABLE ENTRY NAME FUNCTION MANAGER PROFILE TRANSMISSION SERVICES PROFILE PRIMARY LOGICAL UNIT PROTOCOL SECONDARY LOGICAL UNIT PROTOCOL COMMON LOGICAL UNIT PROTOCOL RUSIZE SEC PRI 8192 8192 PRIMARY SEND PACING COUNT SECONDARY RECEIVE PACING COUNT SECONDARY SEND PACING COU
56. This causes Unicenter CA XCOM Data Transport to use the user ID and password supplied If a password is not supplied and xcom glb is checked the transfer will fail due to the invalid ID and password in the xcom glb file on the NT side Trusted Access Home Directory Windows NT 2000 and XP Note If either of these methods is to be successful in the case where Unicenter CA XCOM Data Transport for z OS is sending to Unicenter CA XCOM Data Transport for Windows NT the Unicenter CA XCOM Data Transport for z OS default table MUST have USEROVR YES USEROVR YES is the default This allows the user ID in the MVS JCL to override the batch job ID For information on the USEROVR parameter see the Unicenter CA XCOM Data Transport for z OS Administrator Guide Unicenter CA XCOM Data Transport for Windows NT Server Professional supports Trusted Access To use the Trusted Access feature when transferring to Windows NT platforms note the following m The USEROVR and USERPO default table parameters for Unicenter CA XCOM Data Transport for z OS must be set to YES m Specify USERID single quotes separated by a blank and no passwords in the parameters for the transfer m The user ID must be configured for Trusted Access on the Windows NT partner For more information see the Unicenter CA XCOM Data Transport for Windows NT Server Professional documentation A Windows NT user can have a default home directory assigned by the Windows NT ad
57. authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec SUSPEND destname ownername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination involved in the transfer m ownername the user ID under whose security authorization the transfer is performed Immediately halts and purges an active transfer F XCOM TERM Zuname nnnnnn The following operands are used with the TERM command Operand Description luname Specifies the name 1 to 8 characters of the single session SNA LU that you wish to terminate nnnnnn Specifies the request number 0 to 999999 of the active file transfer that you wish to terminate This operand is required for transfers with a TCP IP partner or with a parallel sessions SNA LU partner Operation and Control 6 45 Using the Unicenter CA XCOM Data Transport MODIFY Commands Notes For SNA transfers TERM stops the LU 6 2 conversation but it does not terminate the session Use the CANCEL command to terminate the session If multiple transfers are running with the same request number the first one shown with the DISPLAY command is the one affected by the TERM command For greater control we recommend using the ISPF or CICS menu interface Command Security Requirements 6 46 User Guide The
58. example filenames and compression The local system then waits for confirmation of the header record information 4 Oncethe contents of the header record are verified Unicenter CA XCOM Data Transport begins sending data records to the remote system Unicenter CA XCOM Data Transport sends each data record checking to see if any sending errors occur If no errors are found the local system checks for an end of file marker denoting the last record of the file If no end of file marker is found another data record is sent 5 Ifanend of file marker is found the local system sends a trailer record that indicates the number of data records sent The local system then awaits Introduction 1 11 Successful Send File Transfer Scenario 1 12 User Guide verification from the remote system that the number of records received is equal to the number of records sent If the number of records matches a successful send file message is sent to the user on the local system and the conversation ends If notification was specified Unicenter CA XCOM Data Transport on the remote system notifies the user of a successful transfer Successful Send File Transfer Scenario Send File Flowchart The following flowchart illustrates a normal Unicenter CA XCOM Data Transport send file request Start User requests transfer CA XCOM Data Transport verifies information for example local file name Display error End message Establish connecti
59. plus a byte compaction scheme that is suitable for uppercase English text COMPACTL Same as COMPACT above only the compaction scheme is most beneficial for lowercase English text LZSMALL Lempel Ziv 77 compression with a small memory allocation scheme LZMEDIUM Lempel Ziv 77 compression with a medium memory allocation scheme LZLARGE Lempel Ziv 77 compression with a large memory allocation scheme HUFFMAN Greater compression than RLE but not as much as the Lempel Ziv 77 modes LZRW3 General purpose algorithm that runs fast and gives reasonable compression The Menu Interface TSO ISPF Panels 2 73 Submit Job To Another System Screen Pack Data Records 2 74 User Guide Value Definition ZLIB n Greater compression than LZRW3 but less than LZSMALL LZMEDIUM and LZLARGE The n value can be 1 through 9 Default YES Specifies whether record packing is to be used on a file transfer Value Definition NO Specifies that no record packing is used The data are sent unblocked LENGTH Specifies that the records are to be packed into fixed size data transfer blocks Each record begins with a 2 byte long prefix that indicates the length of the record and determines how many records can be packed into a block The default block size is 2K but it can be increased to 31K by using the MAXPACK parameter in the Unicenter CA XCOM Data Transport Default Options Table or in the Unicenter CA XCOM Data Transport control library mem
60. scheme HUFFMAN Greater compression than RLE but not as much as the Lempel Ziv 77 modes LZRW3 General purpose algorithm that runs fast and gives reasonable compression ZLIB n Greater compression than LZRW3 but less than LZSMALL LZMEDIUM and LZLARGE The n value can be 1 through 9 Default YES Truncate Record Code Table Receive File From Another System Screen Specifies how records exceeding the maximum logical record length LRECL are to be handled Value Definition Y Specifies that records larger than the maximum LRECL are to be truncated to the maximum record length N Specifies that Unicenter CA XCOM Data Transport is to terminate the file transfer upon receiving a record larger than the maximum LRECL Notes This field is supported only by the Unicenter CA XCOM Data Transport mainframe products Unicenter CA XCOM Data Transport for z OS Unicenter CA XCOM Data Transport for VSE and Unicenter CA XCOM Data Transport for VM When a record is truncated the data not within the LRECL limit is lost Default N This is a 3 character alphanumeric field used for specifying the translation table to be used by the remote partner for this particular transfer only This field is applicable only for transfers to Unicenter CA XCOM UNIX or Windows 2000 2003 or XP partners and only if their INTERNAL CONVERSION TABLES NO Value Definition 1 to 3 bytes Specifies up to alphanumeric characters identifying the
61. system has been received Transfer is not yet scheduled Transfer is scheduled but is waiting Transfer is currently in progress Transfer has been suspended on the local system Transfer has been suspended by the remote system Transfer has completed successfully Transfer has failed Transfer received a VTAM error and will be retried The module name and entry point for this exit is XCOMEX06 How to Enable Specify 06 in the Default Options Table to enable this exit User Exits 0 13 User Exit 6 Calling Module Entry Method Required DSECT The module XCOMEXIT calls this exit This exit is a branch entry EXO6PLST is the required DSECT Addressing Mode at Entry Registers at Entry Registers at Exit Valid Return Code D 14 User Guide The addressing mode at entry is 31 The following registers are available at entry Register Description RO Undefined R1 Address of 6 5 R2 to R12 Undefined R13 Address of register save area R14 Return address R15 Entry point address The following registers are available at exit Register Description RO to R14 Undefined R15 Return code The only valid return code is 0 for a normal return Note The return code from the exit is passed in field EXO6RC of the exit parameter list which is mapped by the EXO6PLST macro found in CAI CINBOMAC User Exit 7 Sample Program User Exit 7 Purpose The following is a sample program us
62. 03 20 XCOM DEFHIST 03 03 20 03 04 07 DA1SZ95 DEFQSAM 45 03 03 20 03 04 07 DA1SZ95 DEFRRDS 03 03 20 03 04 07 DA1SZ95 DFHTCT 03 03 20 03 03 20 XCOM INSTJCL 03 03 20 03 03 20 XCOM ISR PRIM 03 03 20 03 03 20 XCOM LINKACF2 03 03 20 03 03 20 XCOM SAMPCOB 03 03 20 03 03 20 XCOM XCOM 03 03 20 03 03 20 XCOM XCOMACF 2 03 03 20 03 03 20 XCOM XCOMADMT 03 03 20 03 03 23 DA1EG79 XCOMDEST 03 03 20 03 03 20 XCOM XCOMDFLT 03 03 20 03 03 23 DA1EG79 XCOMEX01 03 03 20 03 03 20 XCOM XCOMEX02 03 03 20 03 03 20 XCOM 2 106 User Guide Member Selection List The display screen follows the format established for the ISPF Copy function ISPF Option 3 3 and contains two fields into which the user may enter data Field and location Line command left of the member name User right of the member name Definition Selects a member for a file transfer Enter a letter S in this field to select that member for file transfer Note Multiple members may be selected for transfer only if the Queue for Execution field in the Primary Menu has been set to N indicating that the transfers are not to be queued but will execute immediately Indicates a new name applicable when the member is stored on the remote system and displays the results of a member selection A value of SELECTD indicates that Unicenter CA XCOM Data Transport has successfully selected this member and has generated parameters for its transf
63. 26 i Receive File From Another System TURKI01 Transfer ID Local File Name IP Name Addr 122 222 222 222 Remote File Name MYFILE Program Library NO Create Replace Add C R A C Record Separators Y N N EBCDIC Binary ASCII E B A B Truncate Record Y N z Code Table Remote System Information Execution Priority Secure Socket SSL NO Checkpoint Count Compression Mode Pack Data Records N C L Transfer User Data System User Data Local System Information Tape Y N TURKIO1 Tape Y N Password Domain Notify User Volume PFK 1 Help COMMAND gt F1 Help F7 UP LOG TURKIOI Unit 11 Hold Unit 3 End 12 Alloc F6 RCHANGE F12 Alloc F3 End F9 SWAP F4 RETURN F5 RFIND FlO0 Language F11 Hold F2 SPLIT F8 DOWN Parameter Fields The parameter fields of the Receive File screen are described in the following Transfer ID Associates a descriptive identifier with this file transfer It complements the request number assigned by Unicenter CA XCOM Data Transport to every locally initiated transfer Value Definition xxxxxxxxxx Specifies up to ten alphanumeric or national characters identifying the file transfer Notes The Unicenter CA XCOM Data Transport transfer IDs form a sequence that starts with 001 and is incremented by 1 for each transfer Default Your TSO user ID uuuuuuu with a sequence number nnn appended that is uuuuuuunnn 2 80 User Guide E
64. 34 RESUME 6 35 RSHOW 6 36 SHOW 6 38 SNAP 6 39 STOP 6 42 SUSPEND 6 44 TERM 6 45 TRACE 6 47 VERSION 6 48 XRSHOW 6 49 XSHOW 6 51 XTRACE 6 52 multiple transfers 3 45 3 74 errors 3 11 MVS 9 4 Console Routing Code 3 18 console routing codes 6 16 Message Descriptor Code 3 16 message descriptor codes 6 16 N NETNAME PARM parameter 3 21 NetView and Unicenter CA XCOM Data Transport 6 5 network levels send file flowchart 1 12 logical and physical components A 1 LU A 1 parts of A 1 procedure correlation identifier A 2 session A 2 Network Job Entry 5 2 NEWXFER SYSIN01 parameter 3 45 NJE See Network Job Entry notify user Receive File From Another System screen local system 2 94 2 98 Send File screen local system 2 32 2 36 remote system 2 62 2 77 Send Report screen 2 62 2 64 Submit Job screen 2 76 2 79 Index 7 NOTIFY SYSINOI parameter 3 46 NOTIFYNAME SYSINO1 parameter 3 47 NOTRACE MODIFY command 6 30 Novell NetWare 9 6 NOXTRACE MODIFY command 6 31 NSASTAT MODIFY command 6 32 only save SYSINO1 Selection menu 2 13 OpenSSL 8 2 OpenVMS 9 8 OpenVMS Alpha 9 8 OpenVMS VAX 9 8 operating and controlling Unicenter CA XCOM Data Transport 6 1 operator control parameter fields 2 110 Selection menu option 2 5 OS 2 9 10 OTHERR status field 2 119 PACK SYSINOI parameter 3 59 panels using 2 1 parallel session start 6 13 p
65. 5 Immediate command response 0400 6 Job status 0200 7 Application program processor 0100 8 Out of line message 0080 9 Status display 0040 10 Dynamic status display 0020 11 Critical eventual action required 0010 12 Important information message 13 Reserved for future use Notes The message descriptor codes are selected by the bit configuration where bit 0 corresponds to descriptor code 1 These codes are assigned to error messages ending with The descriptor code is used by Unicenter CA XCOM Data Transport when issuing WTO macro instructions z OS inserts an indicator at the start of the message The indicator is a blank space followed by a sign Default 0200 The Batch Interface 3 13 PARM Parameters EROUT 3 14 User Guide Specifies the sixteen bits coded in hexadecimal of z OS console routing codes for messages ending with E The following are available routing codes Value Descriptor Definition hexadecimal Codes 8000 1 Master console action 4000 2 Master console information 2000 3 Tape pool 1000 4 Direct access pool 0800 5 Tape library 0400 6 Disk library 0200 7 Unit record pool 0100 8 Teleprocessing control 0080 9 System security 0040 10 System error maintenance 0020 11 Programmer information 0010 12 Emulators 0008 13 Installation use 0004 14 Installation use 0002 15 Installation use 0001 16 Installation use 0000 none For Unicenter CA XCOM Data Transport use only Codes are
66. Allocation Information screen are described in the following Indicates the name of the new data set being created This is a protected field and retains the value set in the previous screen Value Up to 256 alphanumeric characters Value Up to six alphanumeric characters Value Up to eight alphanumeric characters Value BLKS TRKS or CYLS Definition Specifies the name of the new data set being created Definition Specifies the volume on which the new data set should be allocated Definition Specifies the generic unit name of a group of volumes on which the new data set should be allocated Definition Specifies whether the data set should be allocated in blocks tracks or cylinders The Menu Interface TSO ISPF Panels 2 43 File Allocation Information Screen Primary Quantity Value Definition Up to six numeric Specifies the initial allocation request in the above characters space units Secondary Quantity Value Definition Up to six numeric Specifies the secondary allocation request in the characters above space units Directory Blocks This parameter is used only for partitioned data sets Value Definition Up to six numeric Specifies the number of directory blocks Specify 0 characters for sequential data sets Record Format Determines the record format associated with the data set to be allocated Value F FA FB FBA FBM FBS VA VB 2 44 User Guide Definition Fixed
67. Exits D 11 User Exit 5 Registers at Entry Registers at Exit Valid Return Code Sample Program D 12 User Guide The following registers are available at entry Register Description RO Undefined R1 Address of SECDSECT R2 to R12 Undefined R13 Address of register save area R14 Return address R15 Entry point address The following registers are available at exit Register Description RO to R14 Undefined R15 Return code The only valid return code is 0 for a normal return Note The return code from the exit is passed in field SECRTNCD of the exit parameter list which is mapped by the SECDSECT macro found in CAI CINBOMAC The following is a sample program using this exit CAI CINBOSAM 5 User Exit 6 Purpose User Exit 6 This exit point allows execution of a user developed exit routine when certain key points are reached in the progress of a Unicenter CA XCOM Data Transport transfer Conditions of Entrance This user exit is entered under the following conditions m Transfer request is scheduled m Transfer request starts m Transfer request completes m Transfer request fails m Transfer request is aged off the queue Defined Exit States The following states are defined for this exit State QUEUED NULL INACT ACTIVE SUSPEND REMSUSP SUCCESS FAILED VTAM ER Module Name and Entry Point Description Transfer has been scheduled or a request from a remote
68. If the remote system is unavailable and the file transfer request is queued the transfer will execute once the remote system becomes available Queued functions permit a higher degree of processing control For example queued transfers can be prioritized or held from execution until they are manually released This request will be executed immediately Non queued transfers must execute within a specified default timeout duration defined in the Default Options Table or they are aborted The Primary Option Menu APPLID of the CA XCOM Server Specifies the APPLID of the Unicenter CA XCOM Data Transport server on the mainframe that will start the transfer or the Unicenter CA XCOM Data Transport XCOMPLEX Admin Server that will schedule the transfer to an XCOMPLEX Worker Server Required Value Definition xxxxxxxx Specifies the APPLID of the Unicenter CA XCOM Data Transport server or XCOMPLEX Admin Server The APPLID can contain up to eight alphanumeric characters Notes Distributed processing provides the capability of displaying and controlling the queues and the history log of a different Unicenter CA XCOM Data Transport mainframe system To display a list of queues follow these steps 1 Enter the APPLID of the Unicenter CA XCOM Data Transport server whose queue you wish to display or modify OR Enter the APPLID of the Unicenter CA XCOM Data Transport XCOMPLEX Admin Server to display the queues for all the XCOMPLEX Worker
69. K K KOR K KOK OR K K KOR OK KOK K DELETE XCOM TEMPORARY CSD FILE ISI I DELCSD EXEC PGM IDCAMS SYSPRINT DD SYSOUT SYSIN DD DELETE TEMPORARY CSD DELETE XCOM TEMP DFHCSD PURGE CLUSTER Sample Files 37 Sample XCOMFCT Sample XCOMFCT This member contains the CICS FCT entries for the XCOMDFT and XCOMHLP files You must copy the entries into the CICS FCT and assemble the FCT before Unicenter CA XCOM Data Transport can use these files XCOM CICS ENTRIES XCOMHLP CONTAINS DATA FOR HELP SCREENS XCOMDFT CONTAINS DEFAULT DATA FOR XCOM CICS USERS X x X X X DFHFCT TYPE DATASET DATASET XCOMHLP ACCMETH VSAM BUFND 3 BUFNI 3 FILSTAT ENABLED OPENED LSRPOOL NONE gt UPDATE IF NECESSARY RECFORM VARIABLE BLOCKED gt lt gt lt gt lt gt x gt x gt x gt x SERVREQ READ BROWSE X STRNO 2 ii DSN XCOM XCOMHELP VS DISP SHR gt OPTIONAL PARAMETER gt OPTIONAL PARAMETER DFHFCT TYPE DATASET DATASET XCOMDFT ACCMETH VSAM BUFND
70. LCLDS01 DD statement If both are specified the data set defined by LFILE takes precedence Specifies up to 54 characters consisting of the following m 1 to 44 data set name m Anoptional member name enclosed in parentheses Note A wildcard character can be used if transferring between IBM mainframe systems Notes Use an asterisk as the member name to show that all members of a partitioned data set are to be transferred For example the statement LFILE PA YROLL PDS indicates that all members of the PAYROLL partitioned data set are to be transferred Use the prefix followed by an asterisk if all members beginning with a specific prefix are to be transferred For example NAMES PDS AL requests that members AL ALEX and ALICE are all to be transferred The asterisk must be the last character before the right parenthesis The use of wildcards is supported only between IBM mainframe systems and platforms running Unicenter CA XCOM Data Transport Version 3 1 or r11 3 42 User Guide LIST LPASS SYSINO1 Parameters Broadcasts this file transfer to all remote destinations designated on a predefined distribution list Value Definition xxxxxxxx Specifies the name of a distribution list designating where this file should be broadcast Notes GROUP LIST and LU are mutually exclusive parameters One of these parameters must be coded either on the EXEC card or in SYSINO1 Coding more t
71. LOGFREE MODIFY command 6 29 login user name 2 8 LOGMODE PARM parameter 3 21 LPASS SYSINO1 parameter 3 43 LRECL SYSINO1 parameter 3 73 LSR sample JCL C 22 LU A 1 6 2 independent implementations A 5 ILU direct sessions with dependent logical units A 5 independent implementations A 5 independent logical units ILUs A 4 overview A 3 PARM parameter 3 21 PU type A 5 SYSINO1 parameter 3 43 types A 3 LU 6 2 benefits improved throughput 1 7 LUNIT SYSINO1 parameter 3 58 LUNITC SYSINOT parameter 3 70 LUSER SYSINO1 parameter 3 44 LVOL SYSIN01 parameter 3 58 LVOLCT SYSINO1 parameter 3 70 LVOLSQ SYSINO1 parameter 3 70 M Management Class parameter 2 46 maximum entries operator control parameter 2 114 MAXLOC system parameter 6 17 MAXREM system parameter 6 17 MAXTASK system parameter 6 17 member selection list 2 20 screen 2 107 menu interface 2 1 considerations 7 5 default values 2 2 Help facility 2 3 messages 2 122 special feature keys 2 3 starting 2 1 messages menu interface 2 122 MGMTCLAS SYSINO1 parameter 3 45 mode definition C 12 Model 204 transactions 5 2 MODIFY commands 6 4 ACTIVATE 6 7 ALTER 6 8 CANCEL 6 11 CNOS 6 13 DELETE 6 15 DFLT 6 16 DISABLE 6 18 DISPLAY 6 20 DUMP 6 21 DUMPXCF 6 22 ENABLE 6 23 EXIT 6 25 HOLD 6 26 INQ 6 27 LIST 6 28 LOGFREE 6 29 NOTRACE 6 30 NOXTRACE 6 31 NSASTAT 6 32 RELEASE 6 33 RESET 6
72. MVS2 DEST RMT2MVS1 Lyn MVS2 E iain tee u q os PSOTAB LU APPLMVS1 X 51 N OUTPUT DD SYSOUT A MVS1 DEST RMT2 Routing to a Specific Minicomputer Printer Using PSOWAIT The following table provides an example of a Unicenter CA XCOM Data Transport Destination Table that equates the external writer name SYSAS400 with a logical unit on an AS 400 Unicenter CA XCOM Data Transport extracts this report from the JES spool and sends it to the AS 400 After the transmission the report is printed on printer P3 of the AS 400 MYJOB JOB 453W XCOM DEMO MSGCLASS A CLASS J STEP1 EXEC PGM IEBGENER SYSPRINT DD SYSOUT A SYSIN DD DUMMY SYSUT1 DD DISP SHR DSN HOST SEQ FILE SYSUT2 DD SYSOUT A SYSAS400 DEST P3 The PSOWAIT option can be used to control whether output is taken from the JES spool immediately and held in temporary data sets PSOWAIT NO or whether output is allowed to remain on the JES spool until a session is available to transmit it on PSOWAIT NO is the default value Specify NO if m The remote LU is on a leased line m There less than 100 nodes in the Destination Table m The destination is an IP address The Remote Spooling Feature Process SYSOUT 5 9 JES2 Considerations PSOWAIT YES prevents Unicenter CA XCOM Data Transport from scanning the JES spool if a session to send the data on does not exi
73. Message Protocol ICMP Address Resolution Protocol ARP Transmission Control Protocol TCP User Datagram Protocol UDP Telnet File Transfer Protocol FTP Simple Mail Transfer Protocol SMTP Domain Name System DNS Sockets and so on Network Layer Internetwork Layer Transport Layer Unicenter CA XCOM Data Transport in the TCP IP Network The sections that follow provide a summary of the services that each layer of the protocol stack performs in the TCP IP network and a description of the important protocols for Unicenter CA XCOM Data Transport functioning as a TCP IP network node The Network layer provides a set of protocols Token Ring Ethernet and so on that defines how data are transported over different physical networks The protocols of the Internetwork layer provide connection services for TCP IP The protocols in this layer connect physical networks and transport protocols The Internet Protocol IP of this layer integrates different physical networks into a unified logical network known as the Internet and provides for the universal addressing of computers hosts in a internet network IP uses a 32 bit number IP address that identifies both a physical network and a specific computer within that network The IP address is the basic transport mechanism for routing data from a source computer to a destination computer However IP does not ensure a reliable communication because it does not
74. NT also creates an MS DOS style name based on the long name for compatibility with environments where long file names are not always supported ext The file extension used to further identify the file For FAT file systems the extension is up to 3 characters For NTFS and HPFS the extension is included in the long file name limit of 256 characters Note If you do not specify an extension Unicenter CA XCOM Data Transport does not supply a default server name The name of the server share name The share name is network provider dependent For Microsoft Windows networks this is the name of the share For NetWare networks this is the name of the volume Types of Files Supported Unicenter CA XCOM Data Transport supports standard Windows NT file types Remote System Information 9 29 Windows NT 2000 and XP Additional Features File Systems File Access Security 9 30 User Guide Additional features include the following The standard Windows NT file systems are File Allocation Table format FAT Windows NT File System format NTFS High performance File System format HPFS Unicenter CA XCOM Data Transport accesses files locally or from any file server on the Microsoft Windows Network or the NetWare or Compatible Network or any other network provider installed on the Windows NT system For transfers to Windows NT systems running any release of Unicenter CA XCOM Data Transport Windows NT is a secured syste
75. Parameter Bieldss sonos cua 2 43 Send Report To Another System Screen 2 47 Parameter Fields Nr CM 2 48 Remote System Information 24 2 2 61 Local System Information 2 4 2 2 63 Submit Job To Another System 2 2 65 Parameter cedentes E 2 66 Remote System IntormatioD 4 oos nde ones GEE Lure ron 2 75 Local System Information Ges eee ee ee so ESSENSE a A a 2 78 Receive File From Another System Screen 2 2 80 Parameter Peds aur siguen eu 2 81 Remote System Information bri bis 2 92 Local System Information 2 2 2 4 4 2 96 Extended Remote File Name Entry Screen 2 99 Japanese Character Set Support Screen 2 2 2 100 Parameter Piela UE 2 100 File Transfer Scheduling Information Screen
76. Queue as WRITER STEPOO1 EXEC PGM IEBGENER SYSPRINT DD SYSOUT A HOLD NO SYSIN DD DUMMY SYSUT1 DSN XCOM TEST TRANSFER DISP SHR SYSUT2 DD SYSOUT A XCOMABC 5 4 User Guide Sample DEST Member WRITER TYPE DEST WRITER XCOMABC Basics of JES Spool Use IPNAME 141 202 156 2 Destination Definitions Using Unicenter CA XCOM Data Transport you can specify that files appearing in the JES spool with JES DEST or WRITER names specified to Unicenter CA XCOM Data Transport are to be sent automatically to specified LUs IP addresses users a group or a list of destinations A destination can be defined as any of the following If the destination Transfers are tried to Is List Group User destinations in a list The destinations in the list can be LUs or IP addresses The first destination in the group and if that attempt fails the second destination in the group and if that fails the third destination that is in the order that the destinations have been defined in the group The destinations in the group must be LUs For TCP IP Group functions as an alias It may be used as a destination but only one IP destination may be specified for a group A specified user logged onto Unicenter CA XCOM Data Transport To send a report simply create SYSOUT output with a DEST or WRITER that Unicenter CA XCOM Data Transport can associate with a remote computer or a user The Remote Spooling F
77. REGION 5120K PARM ACBNAME XCOMAPPL OVERRIDE DFLT STEPLIB DD DSN CAI CAILIB DISP SHR LOAD MODULES DD DSN CEE SCEERUN DISP SHR IBM LE RUNTIME SYSTCPD DD DSN TCPIP TCPIP DATA DISP SHR IBM TCP IP XCOMCNTL DD DSN amp PREFIX XCOMCNTL DISP SHR CONTROL LIBR XCOMRRDS DD DSN amp PREFIX RRDS DISP SHR ACTIVE REQSTS XCOMHIST DD DSN amp PREFIX DISP SHR DONE REQUESTS XCOMREQ DD DSN amp PREFIX XCOMREQ PATH DISP SHR ACCESS PATH XCOMUSER DD DSN amp PREFIX XCOMUSER PATH DISP SHR ACCESS PATH XCOMIDNT DD DSN amp PREFIX XCOMIDNT PATH DISP SHR ACCESS PATH XCOMRECP DD DSN amp PREFIX XCOMRECP PATH DISP SHR ACCESS PATH SYSPRINT DD SYSOUT TCP IP MSGS SYSTERM DD SYSOUT TCP IP MSGS OBO k k THE FOLLOWING XCOMPRNT DD STATEMENT DEFINES THE SYSOUT FOR THE MESSAGES WHEN PDSE PROGRAM LIBRARIES ARE TRANSFERRED YOU MAY SET THIS TO DD DUMMY IF YOU DO NOT WISH TO SEE THESE d MESSAGES XCOMPRNT DD SYSOUT MSGS OCICS ICI IIS ICI THE FOLLOWING SYSMDUMP DD STATEMENT DEFINES A SYSTEM DUMP DATA SET THIS DATA SET SHOULD BE GIVEN THE SAME SPACE ui ALLOC
78. RNOTIFYNAME must also be specified Default LOG The Batch Interface 3 49 SYSINO1 Parameters RNOTIFYNAME Identifies the entity on the remote system that is to receive a notification of transfer completion Value XXXXXXXX Notes Definition Specifies the name up to eight alphanumeric characters of the remote system entity to be notified by the target system when a transfer completes This parameter must be used when RNOTIFY CICS RNOTIFY ROSCOE or RNOTIFY ALL has been selected If you specify RNOTIFY ROSCOE you must also specify RNOTIFYNAME roscoe key If you specify RNOTIFY ALL you must also specify RNOTIFYNAME mailbox name SECURE_SOCKET Specifies whether to use an OpenSSL socket or non OpenSSL socket for transfers Value YES Description Performs a secure transfer The transfer uses an OpenSSL socket and must to connect to an SSL listener on the remote partner NO Default NO 3 50 User Guide Performs a non secure transfer The transfer uses a non OpenSSL socket SPRTY STARTDATE SYSINO1 Parameters Indicates the scheduling priority of this file transfer request When multiple file transfer requests are eligible for initiation that is they are past their start date time to the same LU or GROUP those with higher SPRTY values are scheduled first One is the lowest priority Value Definition 1 to 255 Specifies a scheduling priority for this file transfer request The
79. Resource Name UPDATE XCOM applsec DUMPXCF The applsec variable represents the value of the APPLSEC parameter in the Default Options Table Note The DUMPXCF command should only be used when requested by Unicenter CA XCOM Technical Support ENABLE Command Format Operands Enables a Unicenter CA XCOM Data Transport control library member F XCOM membername The following operand is used with the ENABLE command Operand Description membername Specifies the name of the control library member to be enabled The member name can be up to eight characters long Operation and Control 6 23 Using the Unicenter CA XCOM Data Transport MODIFY Commands Notes This command enables a control library member in the control library The control library contains configuration definitions for Unicenter CA XCOM Data Transport partner destinations distribution lists and customized code page conversion tables To alter an existing definition you must edit the control library PDS member issue a DISABLE command for that member and then issue the ENABLE command The LIST command is used to display an enabled control library member If you want the member to be enabled when Unicenter CA XCOM Data Transport is started you must add the member name to the Unicenter CA XCOM Data Transport start up list member The default name of the start up list member is XCOMSTRT but another name can be specified on the START parameter in the Un
80. Sample Files For more information about the transfer request types see the TYPE parameter in PARM Parameters in this chapter XCOMJOB TYPE EXECUTE Sample In the XCOMJOB TYPE EXECUTE sample a file from the local system is sent to replace a file on a remote system through the execution of a non queued Unicenter CA XCOM Data Transport transfer The EXEC statement includes a PARM parameter used to pass instructions to XCOMJOB concerning the ACB name XCOMJOB TYPE SCHEDULE Samples In the XCOMJOB TYPE SCHEDULE samples a file from the local system is sent to replace a file on a remote system through the execution of a queued Unicenter CA XCOM Data Transport transfer The EXEC statement includes a PARM parameter used to pass instructions to XCOMJOB concerning the ACB name The Batch Interface 3 3 XCOMJOB Sample JCL XCOMJOB TYPE INQUIRE Samples 3 4 User Guide In the XCOMJOB TYPE INQUIRE samples the job uses TYPE SCHEDULE to initiate two file transfers and TYPE INQUIRE to examine the status of those file transfers TYPE INQUIRE does not initiate file transfers unlike the TYPE EXECUTE and TYPE SCHEDULE modes but examines the status of transfers that were previously initiated by TYPE SCHEDULE It waits until the transfers have completed and issues a return code reflecting the status of the transfers The primary use of TYPE INQUIRE is in batch job streams where some job steps are dependent upon the successful completion of oth
81. Servers connected to the same XCOMPLEX Admin Server Note that you cannot modify queue information in this display 2 Select option 3 XCOM Operator Control By specifying a remote system s Unicenter CA XCOM Data Transport APPLID you can carry out third party processing which allows you on the local system to initiate Unicenter CA XCOM Data Transport requests between two remote systems For more information about using this field for third party initiated file transfers see the LUSER parameter The Menu Interface TSO ISPF Panels 2 11 The Primary Option Menu Unicenter CA XCOM Data Transport Default Member Name Specifies the name of an alternate Unicenter CA XCOM Data Transport default table to use Value Definition xxxxxxxx Specifies the name of an alternate Unicenter CA XCOM Data Transport default options table This name can be one to eight alphanumeric characters Default XCOMDFLT XCOMCNIL Data Set Name Specifies an alternate Unicenter CA XCOM Data Transport control library to be used for this transfer Value Definition xxxx xxx xxxxxxxx Specifies the name of an alternate Unicenter CA XCOM Data Transport control library to be used for this transfer The control library name is a data set name Notes This parameter is only used for non queued transfers Queue for Execution N 2 12 User Guide The Primary Option Menu Save SYSINO1 in DS Name Specifies a data set name where Unicenter CA XCOM Data Tr
82. THE SMALLER VALUE WHEN THE PARTNER COMPUTER BINDS WITH ITS OWN RU SIZE VALUE A NOTE ABOUT NAMES USED SNA REQUIRES THAT BOTH COMPUTERS STARTING A SESSION USE THE SAME MODE NAME IN AN LU 6 2 BIND THEREFORE WE STRONGLY RECOMMEND THAT YOU USE THE NAME XCOMMODE THE FIRST EXAMPLE BELOW AS THAT IS THE NAME USED IN ALL THE PARTNER CA XCOM EXAMPLES AND DOCUMENTATION IF YOUR INSTALLATION S NAMING STANDARDS REQUIRE YOU TO SELECT A DIFFERENT NAME YOU MUST PROVIDE THE NEW NAME TO ALL OTHER CA XCOM INSTALLATIONS WITHIN YOUR NETWORK A NOTE ABOUT MODE TABLES XCOM WILL TRY TO OVERRIDE THE CURRENT MODE ENTRY IN YOUR LU DEFINITION FOR THE PARTNER COMPUTER DOING THIS INSURES THAT YOU DO NOT HAVE TO CREATE ADDITIONAL LU DEFINITIONS FOR EACH XCOM USER THERE IS ONLY ONE LIMITATION HOWEVER VTAM REQUIRES THAT THE CA XCOM MODE ENTRY IS IN THE SAME MODE TABLE AS THE CURRENTLY DEFINED MODE ENTRY THEREFORE WE ENCOURAGE YOU TO ADD THE XCOM ENTRY OR ENTRIES TO YOUR EXISTING MODE TABLE S PLEASE DO NOT CREATE A SEPARATE TABLE FOR XCOM ONLY A NOTE ABOUT PARALLEL SESSIONS AND INDEPENDENT LOGICAL UNIT IF YOU WISH TO USE INDEPENDENT LOGICAL UNIT ILU OR PARALLEL SESSION SUPPORT THE IBM DEFINED MODE ENTRY SNASVCMG MUST BE IN THE SAME MODE TABLE AS THE CA XCOM MODE ENTRY COMTABL MODETAB XCOMMODE MODEENT LOGMODE XCOMMODE FMPROF X 13 TSPROF X 07 PRIPROT X BO SECPROT X BO COMPROT X 50B1 RUSIZES X 8686 PSNDPAC 5 SRCVPAC
83. TSO ISPF Panels 2 115 Unicenter CA XCOM Data Transport Transfer Request Display Screen Protected Display Fields Fields on the Unicenter CA XCOM Data Transport Transfer Request Display screen that are informational and cannot be overwritten have the same meanings as their counterparts on the screens used to define a file transfer request Note The USERID field displays the local user ID designated when this file transfer request was made Status Fields The rightmost column on the Unicenter CA XCOM Data Transport Transfer Status Display screen indicates the status of each displayed file transfer The terms used to indicate transfer status in Unicenter CA XCOM Data Transport are listed and explained in the following table Status Term ACTIVE CANCLD COMPLT HELD INACT LOCFER 2 116 User Guide Explanation The transfer is currently in progress The transfer was cancelled before it began executing compare with the TERMTD status The transfer has completed successfully The transfer is being held and must be released manually to be eligible for execution To release the transfer enter A in the S field The transfer is pending and eligible to begin as soon as it reaches its start time date If the transfer s start time has been reached and the transfer has not started Unicenter CA XCOM Data Transport may be waiting for a session to become available or be established or the transfer request may not have reached
84. TYPE SCHEDULE transfers there are several potential complications to consider a When LCLDS01 is used to reference a local file for a transfer the z OS JCL processor is involved in the data set allocation process for the transfer It is possible to encounter problems with data set enqueues being held by 2 5 allocation routines while the transfers are being scheduled m Ifthe transfer begins to run on the started task before the job scheduling transfer ends the data set may not be available for exclusive use by the Unicenter CA XCOM Data Transport started task This may cause the transfer to fail due to an unavailable exclusive enqueue m Using LCLDSOI to reference a local file for a transfer may also lead to the creation of dummy GDGs If the LCLDSO01 DD is used to create a 1 GDG version for a TYPE SCHEDULE transfer there are additional potential problems When the z OS JCL performs the allocation of the LCLDSO01 DD it allocates and potentially catalogs the new version depending on the value of the DISP parameter in the JCL This new version does not have an end of file mark because it has not yet been opened and closed by a program The Batch Interface 3 5 XCOMJOB DD Statements JOBLIB or STEPLIB SYSINO1 3 6 User Guide When the transfer begins on the Unicenter CA XCOM Data Transport started task it allocates a new 1 version of the GDG In cases where the transfer is successful this results in the creation of t
85. The Unicenter CA XCOM Data Transport partner can be identified with any one of the following m A valid SNA LU name m ATCP IP name m ATCP IP address The Unicenter CA XCOM Data Transport partner name destname must match that which is shown by the DISPLAY command If there is no active session with the partner an error message is displayed Cancels the session immediately causing the transfer to be interrupted and requeued It is automatically retried after the error interval expires if GETSESS YES is specified or when the session becomes available if GETSESS YES is not specified Cancels the session immediately causing the transfer to abort The transfer is terminated unconditionally that is it cannot be restarted but must be rescheduled from the beginning Cancels the session immediately causing the transfer to be interrupted and suspended The transfer remains suspended until it is reactivated with the RESUME command Operation and Control 6 11 Using the Unicenter CA XCOM Data Transport MODIFY Commands Notes If no operand is coded following the Unicenter CA XCOM Data Transport partner name destname or and the transfer is active on the session the session is canceled when the transfer completes For IMMED and SUSPEND if checkpointing is active for the transfer it is restarted from the most recent checkpoint Command Security Requirements 6 12 User Guide The use of the command requires that the com
86. VSAM defaults to 20 of the primary allocation Zero may be specified if you do not want any secondary allocation VSE Part Description catalog id Optional for output files Defines the name of the user catalog that will own the data set You may leave this field blank if the master catalog owns the data set Note The use of VSAM managed SAM files requires IBM s IDCAMS program to be dynamically loaded in the partition This requires an additional 130K partition GETVIS storage DTF Information VSE file characteristics must be predetermined when creating the files If sending to or receiving from a VSE system you must specify the following m The record format which can be either fixed F fixed blocked FB variable V or variable blocked VB m The logical record length LRECL indicates the number of characters in the longest record in the file m The block size BLKSIZE which can be either equal to the LRECL for fixed files a multiple of the LRECL for fixed blocked files the LRECL 4 for variable files or the BLKSIZE 4 for variable blocked files Types of Files Supported IBM VSE supports VSAM RRDS KSDS and ESDS and SAM files Restrictions The following restrictions apply to Unicenter CA XCOM Data Transport for VSE m NoFILEOPT ADD for receiving VSE Unicenter CA XCOM Data Transport for VSE does not support FILEOPT ADD if the VSE is receiving the file m No Checkpoint Restart for SAM Unic
87. Value Definition B Indicates binary data E Indicates that the data is in EBCDIC code A Indicates that the data is in ASCII code Note EBCDIC packed decimal fields cannot be transferred under EBCDIC Use BINARY to transfer EBCDIC packed decimal fields Default E Secure Socket SSL Checkpoint Count Receive File From Another System Screen Informs Unicenter CA XCOM Data Transport how to handle the security of the transfer to the remote system Value Definition YES Tells Unicenter CA XCOM Data Transport to use OpenSSL for the transfer of the file and that it must connect to a SSL port on the remote partner NO Tells Unicenter CA XCOM Data Transport that the file does not require a secure connection and should be handled as a regular file transfer Specifies the interval at which Unicenter CA XCOM Data Transport takes a checkpoint to be used to restart a suspended or failed file transfer The length of the checkpoint interval is measured in terms of a number of blocks Value Definition 0 Specifies that Unicenter CA XCOM Data Transport is to take no checkpoints 1to9999 Specifies the number of blocks that form a checkpoint interval A checkpoint is taken whenever the specified number of blocks has been transferred Note If record packing is not used 1 record 1 block Each time a checkpoint is taken the output buffers on the receiving system are written to the disk Making the checkpoint interval too short will
88. XCOM Data Transport On an AS 400 or VAX system the operator console is notified Default LOG The Menu Interface TSO ISPF Panels 2 77 Submit Job To Another System Screen Local System Information User ID 2 78 User Guide The Local System Information parameter fields of the Submit Job screen are described in the following Identifies the user ID under whose set of resource access privileges this file transfer is to execute on the source computer Value Definition xxxxxxxx Specifies up to eight alphanumeric characters representing the user ID whose privileges are used for executing this file transfer on the source computer Notes This information is primarily used for third party processing For example a Unicenter CA XCOM Data Transport node in New York could request that a Unicenter CA XCOM Data Transport node in Los Angeles send a file to a Unicenter CA XCOM Data Transport node in Chicago To use this feature all systems must be identified to VTAM and running Unicenter CA XCOM Data Transport Version 2 or higher For conventional non third party file transfers use this parameter to identify the user that initiated the transfer This is useful when performing operator tracking and control functions through the Unicenter CA XCOM Data Transport Operator Control screen To send a blank parameter value to the source system enter inserting at least one blank space between the quotation marks Do this when the so
89. XCOM Data Transport defaults to the ID associated with the address space that submitted the file transfer request SYSINO1 Parameters XCOM CONFIG SSL For example if there is a JCL USERID parameter coded in the JOB statement of the job invoking XCOMJOB then that JCL USERID is used If a blank USERID parameter value is to be sent to the remote system USERID must be entered with at least one space between the quotes Do this if the remote system is to supply its own default for the user ID under whose access privileges this transfer is to execute Specifies the HFS SSL configuration file path and file name Value Definition 1 to 256 Specifies the HFS path and file name of the SSL configuration file characters used by Unicenter CA XCOM Data Transport for secure transfers Note A sample SSL configuration file configssl cnf is provided with the installation Default None The Batch Interface 3 55 SYSINO1 Parameters SYSINO1 Parameters Required by FILETYPE FILE The following additional parameters can be used only when FILETYPE FILE has been indicated FILE Provides file information for a transfer This information depends on the type of transfer and the systems being used Value Definition Up to 256 If TYPE SEND specify the remote file to which data is alphanumeric transferred characters TYPE RECEIVE specify the remote file being transferred If the remote system is a z OS computer specify the data se
90. XXC000270 ERROR RETRY INTERVAL XXC000280 ENABLE DISABLE TYPE EXECUTE SUPPORT 000290 ENABLE DISABLE EXIT 1 SUPPORT XXC000300 ENABLE DISABLE EXIT 2 SUPPORT XXC000310 ENABLE DISABLE EXIT 3 SUPPORT XXC000320 ENABLE DISABLE EXIT 4 SUPPORT XXC000330 ENABLE DISABLE EXIT 5 SUPPORT XXC000340 ENABLE DISABLE EXIT 6 SUPPORT XXC000350 ENABLE DISABLE EXIT 7 SUPPORT XXC000360 ENABLE DISABLE EXIT 8 SUPPORT XXC000370 ENABLE DISABLE EXIT 9 SUPPORT XXC000380 ENABLE DISABLE EXIT 10 SUPPORT XXC000390 RESERVED FOR FUTURE USE XXC000400 ENABLE DISABLE EXIT 12 SUPPORT XXC000410 ENABLE DISABLE EXIT 13 SUPPORT XXC000420 FILE ACCESS ERROR RETRY LIMIT XXC000430 Sample Files Sample XCOMDFLT Macro Member XCOMDFLT C 16 User Guide GETSESS NO IDESC 0200 INQWATT 000100 IPPORT 8044 IROUT 4020 JESINTV 60 JESOPER JOBACB XCOM LDATACLS LDSNTYPE LIBNEG YES LMGMTCLS LOG YES LOGCL X LOGDEST LOGMODE XCOMMODE LOGNREQ NO LOSERS 4 LSTORCLS LUSECURE NO LU6ABND TERMINATE MAXDEL 32 MAXLOC 75 MAXPACK 31744 MAXREM 75 MAXRPTB 32760 MAXTASK 150 MSGFMT XCOM MSTRCATU YES NETNAME XCOMAPPL NETMAST NO NTFYTPN XCM1 OPERLIM 5000 OPERSEC NONE PRI 10 PSOCKPT 1000 PSODISP DELETE PSOPREF XCOMPSO PSOSECUR NO PSOUNIT SYSALLDA PSOVOL PSWDCHK YES RECVRID RELEASE REMAGE 5 ROSPROC ROSCOE ROUND SEC 5 SECURE SOCKET NO SECURITY NONE SERL 255 SERVADDR SERVPORT 8044 SMF NO SMFNU
91. a blank parameter value to the remote system enter inserting at least one blank space between the quotation marks Do this when the remote system supplies its own default value for the user ID under whose access privileges the file transfer is to execute on the remote system Default The last remote user ID entered The Menu Interface TSO ISPF Panels 2 91 Receive File From Another System Screen Tape Password 2 92 User Guide Indicates whether the remote data set resides on magnetic tape Value Definition Y Specifies that the remote data set resides on magnetic tape N Specifies that the remote data set does not reside on magnetic tape Notes If you enter Y in the Tape field a new screen MVS Extended Tape Parameter Entry is displayed allowing tape related information to be specified See the section MVS Extended Tape Parameter Entry Screen earlier in this chapter Default N Identifies the password associated with the remote user ID Value Definition Up to 31 Specifies up to 31 alphanumeric characters representing the alphanumeric user password associated with the remote user ID characters Notes If the remote system is running IBM eTrust CA ACF2 Security or eTrust CA Top Secret Security this parameter can be used to change the password on the remote system To do this use the following format oldpassword newpassword Receive File From Another System Screen Domain Notify Use
92. a eR tta Er Ebr dub uice b bu TIAE 6 5 8 2 e moni en m een 6 6 vi User Guide ACTIVATE Command 6 7 ALTER Command 6 6 CANCEL Command 6 ruru ade edd REI AIO DOE da 6 11 CNOS Command 6 13 DELETE Comnbiand 2 22 22 42244 44444 42444 4244 6 15 COMMANA 6 16 DISABLE Command ded LER PAR eA Ad 6 18 DISPLAY Command 2212 2o desde quie de odd tede quide qe dde die dudes 6 20 DUMP 2 2 6 21 DUMPXCE Coznpiuand eoe Qui OE dU Vou Edo 6 22 ENABLE 6 23 EXIT 1 22 2 2 6 25 HOLD Command 6 26 INO Command lt zz zg Said da wa deals dala esce sei ac duis oe are 6 27 LIST Command etui a dae oie hee a 6 28 LOGFREE
93. appears to the right on the same line The second item in the Remote System Identification field is a specific destination name or a number in the case of an IP address You cannot change the destination type for instance SNA LU Name to XCOM Group Name but you can change the specific destination name or number Default The remote destination specified on the Primary Option Menu The Menu Interface TSO ISPF Panels 2 19 Send MVS File To Another System Screen Port Dropsess 2 20 User Guide Specifies the number of the IP port where Unicenter CA XCOM Data Transport listens at the remote system Note This field is displayed on the screen only when an IP name or address is referenced in the Remote System Identification field Value Definition 1 to 65535 Identifies the IP port monitored listened to by Unicenter CA XCOM Data Transport at the remote system Notes If this field is left blank the port value specified in the Unicenter CA XCOM Data Transport Default Options Table is used Specifies whether a session with a Unicenter CA XCOM Data Transport partner should be terminated at the completion of a file transfer Optional Note This field is displayed only when an SNA type of partner is referenced in the Remote System Identification field Value Definition Y Indicates that the session is to be terminated after the transfer has completed N Indicates that the session is to be retained after the transfer has comp
94. chart 01 January 02 February 03 March 04 April 05 May 06 June 07 July 08 August 09 September 10 October 11 November 12 December dd is a 2 digit number in the range 01 to 31 designating a day of the month For example to change the start date for request 1084 to June 1 2005 specify F XCOM ALTER 1084 DATE 20050601 yyddd Julian date where yy is a 2 digit designation for a year for example 02 ddd is a 3 digit number in the range 001 to 366 designating a day of the year For example to change the start date for request 1084 to February 1 2005 that is the 32nd day of 2005 specify F XCOM ALTER 1084 DATE 05032 Operand Using the Unicenter CA XCOM Data Transport MODIFY Commands Description EPRTY hhmm nnn nnnnnn SPRTY TIME If no date is coded the default value of DATE is assumed as the new starting date Default Current date Alters the execution priority nnn of the file transfer with request number nnnnnn The new execution priority may be coded in the operand nnn following the keyword EPRTY If the operand nnn is not coded the default value of EPRTY is assumed as the new execution priority If several file transfers are active at the same time the processing priority is given to that transfer that has the highest execution priority number Default 16 Specifies the hour hh and minute when the transfer with request number nnnnnn is to st
95. creating the trace file ipname Specifies the name or address of the IP destination to be traced The trace function dynamically allocates a SYSOUT file to receive the trace data This SYSOUT file s class is defined through the DUMPCL parameter of Unicenter CA XCOM Data Transport s Default Options Table see the Unicenter CA XCOM Data Transport for z OS Administrator Guide It can be overridden in the EXEC PARM of the Unicenter CA XCOM Data Transport started task In most cases the Unicenter CA XCOM Data Transport trace is more desirable than a VTAM buffer trace because it does not require GTF and is simpler to turn on and off To turn off the trace use the NOTRACE command Operation and Control 6 47 Using the Unicenter CA XCOM Data Transport MODIFY Commands Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec TRACE destname The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the luname or ipname for which the trace is activated VERSION Command Format Notes 6 48 User Guide Displays Unicenter CA XCOM Data Transport version information F XCOM VERsion When the VERSION command is issued Unicenter CA XCOM Data Transport responds wi
96. does not support multivolume data sets Consequently neither does the Unicenter CA XCOM Data Transport Menu Interface Use the Batch Interface when processing multivolume data sets Note If the multivolume data set is an output file it must be pre allocated In this situation FILEOPT REPLACE must be used Unicenter CA XCOM Data Transport supports spanned records Version 2 transfers only While Unicenter CA XCOM Data Transport does not specifically support either ISAM Indexed Sequential Access Method or DA Direct Access data sets several utilities for example IEBISAM exist to convert these access methods to sequential files which Unicenter CA XCOM Data Transport does support Processing Different File Types 7 7 File Security Overview of Unicenter CA XCOM 2 Data Transport Security Unicenter CA XCOM Data Transport provides security for four different types of resources The resources that can be secured are the files data in the files commands and LUs or IP destinations This section offers a brief characterization of the essential features of Unicenter CA XCOM Data Transport security as it relates to the various resources Unicenter CA XCOM Data Transport makes calls to IBM RACF eTrust CA Top Secret Security and eTrust CA ACF2 Security to verify whether a given user ID is authorized to read or update a given data set Command Security Unicenter CA XCOM Data Transport makes standard SAF calls to determine w
97. end with CMD The following restrictions apply to CA XCOM for 5 2 APPC limitations Due to the vast number of vendor APPCs and link types supported by CA XCOM consult the APPC vendor s manual for restrictions on the services provided by that vendor These restrictions may impact such features as MVS TYPE EXECUTE transfers environments that you can or cannot send to and so on No library transfers CA XCOM for OS 2 Version 2 does not support library transfers from MVS mainframes No extended attributes CA XCOM for OS 2 does not support the transfer of extended attributes Packing options Versions of CA XCOM for OS 2 prior to Version 3 0 do not support some of the various packing options available on other CA XCOM systems For example they do not support the UNIX packing option carriage flag MPACK Remote System Information 9 11 Stratus Stratus This section contains information about important aspects of the Stratus operating system Naming Conventions Use the following format to name Stratus files top_directory gt group_directory gt home_directory gt filename suffix All names must be unique to that level The following table describes the parts of a Stratus file name Part Description top_directory The physical disks Range 1 to 32 characters group_directory A group of user home directories Range 1 to 32 characters home_directory The user s home directory This directory resides in a grou
98. file The following table lists the maximum logical record lengths for different file types File type Maximum logical record length Disk file 32767 bytes Job RDR file 80 bytes Report PRT file 133 bytes Remote System Information 9 19 VSE VSE VSAM Naming Conventions This section contains information about important aspects of the VSE operating system When accessing a file on a VSE system the Remote file name field indicates the file id as it would be specified on the DLBL an indicator of whether the file is VSAM or SAM and optionally additional information needed for locating the file Format for VSAM File Names 9 20 User Guide Use the following format to name a VSAM file file id N catalog 70 The following table describes the parts of a VSAM file name Part Description file id The name given to the data set when it was defined using IDCAMS by including the following line in the JCL DEFINE CLUSTER NAME file id V Indicates that this is a VSAM file catalog id Optional The name of the user catalog that owns the VSAM data set as defined using IDCAMS by including the following line in the JCL DEFINE USERCATALOG NAME catalog id Leave this field blank if the data set is owned by the master catalog VSE SAM Naming Conventions Format for SAM File Names Use the following format to name a SAM file file id S unit 1ocatzon s7ze override The following
99. file of history records that are not deleted from the history file Generally after running XCOMUTIL and receiving a 0 return code the history file is deleted and redefined Then the HISTOUT file is copied back to the history file SYSIN Used to enter the XCOMUTIL parameters described earlier SYSPRINT XCOMUTIL prints a report providing details about the purge procedure just executed Sample of Required JCL The complete sample JCL can be found in CINBOSAM and is listed in the appendix Sample Files STEP2 EXEC PGM XCOMUTIL COND 0 NE STEPLIB DD DSN XCOM X LOAD DISP SHR SYSPRINT DD SYSOUT HISTIN DD DSN amp amp HSTSAV DISP OLD DELETE HISTOUT DD DSN amp amp HSTNEW UNIT SYSALLDA SPACE CYL 2 2 DISP NEW PASS SYSIN DD 55 15 History and SMF Files 5 XCOMUTIL DD Statements Return Codes The following are XCOMUTIL return codes Return Description Code 0 XCOMUTIL ran successfully 4 XCOMUTIL ran successfully but no history output records were written based on the specified selection criteria 8 XCOMUTIL was unable to open one of the files 12 XCOMUTIL found a parameter error processing the SYSIN file Sample History File Purge Procedure CALCINBOSAM XCOMUTIL contains an example of a four step process that performs the following steps Because XCOMUTIL is an off line procedure remember to first bring Unicenter CA XCOM Data Tran
100. first attempt at session establishment fails a request for session establishment is placed in a request queue A session must be established within the time specified by the SWAIT parameter If no session is established within the specified time a session establishment error is considered to have occurred which results in incrementing the value of the SERL parameter for a description of the SERL parameter see the Unicenter CA XCOM Data Transport for z OS Administrator Guide Job name or started task name of the TCP IP stack that is used by the Unicenter CA XCOM Data Transport TCP IP interface Use this parameter to specify the desired stack if multiple stacks are running at your site Value Definition xxxxxxxx Specifies up to eight alphanumeric characters indicating the job name or started task of the TCP IP stack used by the Unicenter CA XCOM Data Transport TCP IP interface Default None Note An empty value causes the Unicenter CA XCOM Data Transport TCP IP interface to listen on all IP stacks Indicates the maximum duration that Unicenter CA XCOM Data Transport is to wait for any or TCP IP command to complete before terminating the program with an abnormal return code This ensures that the Unicenter CA XCOM Data Transport Batch Interface does not hold up an initiator or socket indefinitely For example if a target computer is unavailable VTAM cannot initiate a session therefore the procedure terminates at the specifi
101. is determined by either the destination member or the default table The LIST parameter is valid only for TYPE SCHEDULE transfers Since a transfer to a list destination is processed as a queued request the various file transfers involved might have different start times Use the Unicenter CA XCOM Data Transport Operator Control function on the Menu Interface to check the current status of any broadcast distribution Specifies whether a log of Unicenter CA XCOM Data Transport activity is written to SYSOUT Value Definition YES Write a log of Unicenter CA XCOM Data Transport activity to SYSOUT NO Do not write a log of activity Notes Unless LOG NO is coded the Unicenter CA XCOM Data Transport activity log includes a list of the SYSINO1 parameters used for the file transfer except for the PASSWORD parameter value which is omitted for security reasons Default YES The Batch Interface 3 19 PARM Parameters LOGCLASS LOGDEST LOGMODE 3 20 User Guide Indicates the desired SYSOUT class to which the Unicenter CA XCOM Data Transport log is written Value Definition X Specifies the SYSOUT class X x Specifies a SYSOUT class other than X This class can be represented with any alphabetic character You can also specify an asterisk which writes the Unicenter CA XCOM Data Transport log to the same class as this job s JCL MSGCLASS Default X Indicates the SYSOUT destination to which the Unicenter CA XCOM D
102. is printed on the remote system DELETE Delete the report file after it is printed on the remote system Default DELETE Indicates the name of the Forms Control Buffer that JES uses from SYS1 IMAGELIB when the report is sent to a remote z OS system Value Definition Xxxx Specifies the name of the Forms Control Buffer that JES uses when the report is sent to a remote z OS system The name can be up to four alphanumeric characters long Default System default value Tells the remote operator the kind of form on which to print a report Value Definition XXXX Specifies up to four alphanumeric characters representing the kind of form on which to print the report Notes If you specify a special form value make certain the value is valid for the remote computer Otherwise the print job fails If in doubt use the default SYSINO1 Parameters REPORT REPORTHOLD Supplies the title of the report Value Definition Up to 21 alphanumeric Specifies the title of the report characters Notes Depending on the operating system printing the report this parameter might only be used as a comment which would not be printed as part of the report It may be part of a banner page produced with the report AS 400 and VAX VMS print this field in a banner page With reports sent to a z OS system this entry becomes part of the banner page The banner page consists of the report title and the values designated in the CLASS and FORM
103. notification C 23 transfer all generations of a GDG 7 5 batch interface 7 4 bytes 2 121 completed B 2 control 3 74 errors during multiple 3 11 fixed to variable 7 7 menu interface 7 5 multiple 3 45 progress user exit D 13 records Detailed File Transfer screen 2 121 scheduled versus immediate 7 4 time secs Detailed File Transfer screen 2 121 VTAM compression bytes 2 121 transfer control XTC parameters See also SYSINO1 parameters HOLDCOUNT 3 75 XTCERRDECR 3 75 XTCERRINCR 3 76 XTCERRPURGE 3 76 XTCERRREL 3 75 XTCGOODDECR 3 76 XTCGOODINCR 3 77 XTCGOODPURGE 3 77 XTCGOODREL 3 77 XTCJOB 3 77 XTCNET 3 78 transfer ID 2 116 Detailed File Transfer screen 2 121 operator control parameter 2 112 Receive File From Another System screen 2 81 Send File screen 2 16 Send Report screen 2 48 Submit Job screen 2 66 transfer log 6 17 transfer queue sample C 1 transfer request 3 74 Transfer Request Display screen 2 114 selection commands 2 117 unprotected fields 2 117 Truncate Record parameter 2 25 2 55 2 72 TRUNCATE SYSINO1 parameter 3 53 truncating records 2 25 2 55 2 72 TSO commands DSPRINT 5 1 PRINTOFF 5 1 VPSPRINT 5 1 requeue data sets 5 7 TSO ISPF Dialog Manager services 2 2 menu interface 2 1 TYPE PARM parameter 3 26 SYSINOI parameter 3 54 TYPE EXECUTE LCLDSO01 DD statement 3 6 RESTART parameter 3 49 return code 3 82 sample transfer C 24 time
104. parameters Designates whether the report should be held or prepared for immediate printing Value Definition YES Hold the report NO Print the report immediately Notes This parameter cannot be used with a Windows or a UNIX partner Default NO The Batch Interface 3 65 SYSINO1 Parameters SPOOL Designates whether to spool the report to disk or to print it directly If the remote computer is a z OS system this operand has no effect on the transfer Value Definition YES Spool the report to disk NO Do not spool print the report immediately Default YES WRITER Specifies the name of the external writer that is to process the report on the remote system Value Definition xxxxxxxx Specifies up to eight alphanumeric characters identifying the external writer that is to process this report on the remote system Notes This parameter may not be specified with Version 1 transfers SYSINO1 Tape Parameters The parameters described in this section can be used when tape drives are involved in the transaction Allowable values for these parameters are the same as for their IBM JCL counterparts except where noted You can also refer to this section for parameter information when using the Menu Interface Note When tape drives are involved in the transaction it may be necessary to use also some of the parameters discussed in the section FILETYPE FILE Parameters such as the parameters LUNIT LVOL UNIT and VOL
105. parameters are accessed on the Submit Job To Another System screen Associates a descriptive identifier with this file transfer It complements the request number assigned by Unicenter CA XCOM Data Transport to every locally initiated transfer Value Definition XXXXXXXXXX Specifies up to ten alphanumeric or national characters associating a descriptive identifier with this file transfer Notes The Unicenter CA XCOM Data Transport transfer IDs form a sequence that starts with 001 and is incremented by 1 for each transfer Default TSO user ID uuuuuuu with a sequence number nnn appended that is uuuuuuunnn Specifies the execution priority for this request Value Definition xxxxxxxxxx Specifies up to ten alphanumeric or national characters representing the execution priority for this request 1 is the lowest execution priority Notes When multiple Unicenter CA XCOM Data Transport transmissions are executing concurrently transfers with higher execution priorities receive preferential service In a busy Unicenter CA XCOM Data Transport environment unless you have compelling reasons for not doing so enhance processing efficiency by giving short file transfers a higher priority value than long running transmissions Default 16 Local File Name File Sequence Submit Job To Another System Screen Indicates the name of the local data set being transferred Required Value Definition Up to 56 Specifies up to 56 charact
106. removes request numbers from the XCOMINO file if the requests are complete or not found Request numbers for transfers that have not completed are not removed from the XCOMINO file The XCOMINQ data set must be preallocated using ISPF or IEBGENER The file cannot be created in a job step There is sample JCL to define the inquire data set in CAI CINBOSAM DEFINQ Define a unique INQUIRE data set for each set of transfers XCOMJOB DD Statements Note It is important to be consistent when using TYPE INQUIRE in an XCOMPLEX environment or it does not work properly If the TYPE SCHEDULE goes directly to an XCOMPLEX Worker Server then the TYPE INQUIRE must also be done against the XCOMPLEX Worker Server If the TYPE SCHEDULE goes through the XCOMPLEX Admin Server then the TYPE INQUIRE must also be sent to the XCOMPLEX Admin Server XCOMJOB DD Statements LCLDSO1 This section explains the DD statements used in XCOMJOB JCL Defines the local data set available for the transfer request The preferred alternative to using the LCLDS01 DD statement is to define the data set using the parameter in the SYSINO1 DD statement see below If you enter both the LCLDS01 DD statement and the SYSINO1 LFILE parameter the LFILE parameter takes precedence You should use the LFILE SYSINO1 keyword parameter to specify the local file name for TYPE SCHEDULE transfers While you can specify the local file name using the LCLDS01 DD statement even for
107. selected by bit configuration where bit 0 corresponds to Routing Code 1 bit 1 corresponds to Routing Code 2 that is at z OS system generation each operator s console is assigned routing codes corresponding to the functions that the installation wants that console to perform Specifying EROUT 0000 in the Default Options Table or as part of the PARM field of the EXEC JCL statement causes the suppression of all XCOMMnnnnE messages from the SYSLOG and most error messages generated by XCOMJOB messages continue to be a part of the Unicenter CA XCOM Data Transport log Default 4020 GROUP PARM Parameters Tells Unicenter CA XCOM Data Transport to use the pooled LU feature to allow for multi threading of transfers to nodes that support multiple logical units but not parallel sessions Value Definition xxxxxxxx Specifies the name of a group of LUs The name be eight characters long The first character of the name must be alphabetic while the rest can be any combination of alphanumeric or national characters Notes GROUP LIST LU and IPNAME are mutually exclusive parameters One of these parameters must be coded either on the EXEC card or in SYSINOT however coding more than one will cause an error The group must be predefined in the Unicenter CA XCOM Data Transport control library CAI CINBOCTL When the transfer process begins Unicenter CA XCOM Data Transport tries transferring to the first LU in the group If
108. space units allocate new 2 43 block size 2 45 directory blocks 2 44 primary quantity 2 44 record length 2 45 secondary quantity 2 44 SPACE SYSINO1 parameter 3 60 split screen 2 3 SPOOL 5 01 parameter 3 66 SPRTY SYSINO1 parameter 3 51 SSL 8 2 start date time 2 103 2 106 2 110 menu interface 2 1 parallel session 6 13 Index 12 User Guide start time unprotected field 2 117 time 2 104 status 2 118 time date LOCATE command 2 116 status 2 118 unprotected field 2 117 STARTDATE SYSINO1 parameter 3 51 STARTTIME SYSINO1 parameter 3 52 status Detailed File Transfer screen 2 121 Transfer Request Display screen 2 118 STCAPPL PARM parameter 3 23 STCIP PARM parameter 3 23 STCPORT PARM parameter 3 23 STEPLIB DD statement 3 6 STOP MODIFY command 6 42 stopping Unicenter CA XCOM Data Transport 6 42 Storage Class parameter 2 46 STORCLAS SYSINOT parameter 3 52 store and forward 9 6 Stratus System 88 9 12 structure defining XCOMPLEX C 19 Submit Job screen 2 65 local system 2 78 parameter fields 2 66 remote system information 2 75 supported programming languages 4 1 SUSPEND MODIFY command 6 44 suspended transfers resuming 6 35 SUSPND status field 2 119 SW AIT PARM parameter 3 24 SYS1 IMAGELIB 2 57 SYSIN DD statement B 5 SYSINO1 data sets 4 1 DD statement 3 6 3 29 LPASS XCOMENCR C 36 PASSWORD XCOMENCR C 36 Selection menu 2 12 XTC 3 74 S
109. the top of the target computer s queue The transfer could not commence because of a problem involving the local file For example it could not be accessed because of a security violation To view the associated error messages select a detailed display by entering either S or D in the S column Unicenter CA XCOM Data Transport Transfer Request Display Screen Status Term Explanation LOGCER The transfer was aborted when the remote computer detected a fatal processing error The remote computer sends at least one descriptive error message to this computer To view the error messages enter either S or D in the S column OTHERR An error that did not fall into the LOCFER LOGCER or VTAMER categories caused this transfer to fail To view the associated error messages enter either S or D in the S column REMSUS The transfer was suspended by a user or an operator on the remote system SUSPND The transfer was suspended by a user or an operator on the local system TERMTD The transfer was terminated by a local operator console command UNKN Contact Unicenter CA XCOM Data Transport technical support if this status is indicated NETERR The transfer was aborted because of a network error The remote computer will send at least one descriptive error message to the initiating computer To view the error messages enter either S or D in the 5 column The Menu Interface TSO ISPF Panels 2 117 Detailed File Transfer Di
110. the user ID and password in uppercase Remote System Information 9 3 z OS z OS This section contains information about important aspects of the z OS operating system Naming Conventions Use the following format to name a 2 5 file data set 1 11 level2 level3 level7 level amp 8 membername The following table describes the parts of a z OS file name Part Description level Required A file name can consist of multiple levels separated by a period Each level has the following characteristics m be up to eight uppercase characters long m Itstarts with either an alphabetic character or a national character 2 There is a limit of eight levels with a total of 44 characters including the separating periods In most z OS environments a data set name is further restricted by security rules created by the installation Contact the appropriate personnel within your organization for details Typically the high level name first level name must match your z OS user ID or some other predefined index membername Required for z OS partitioned data sets only Specifies the particular member in a z OS partitioned data set PDS A PDS is a library containing members that are each separate sequential files The member name is appended to the end of the file name in parentheses Range One to eight alphanumeric or national characters Note Most sites catalog all files through
111. transfer requests for the current Unicenter CA XCOM Data Transport partner Default N Port Print Destination Send Report To Another System Screen Specifies the number of the IP port where Unicenter CA XCOM Data Transport listens at the remote system Note This field is displayed on the screen only when an IP name or address is referenced in the Remote System Identification field Value Definition 1 to 65535 Identifies the IP port monitored listened to by Unicenter CA XCOM Data Transport at the remote system Notes If this field is left blank the port value specified in the Unicenter CA XCOM Data Transport Default Options Table is used Specifies the name of the printer or other device on the remote system that is to receive the report This destination is dependent upon the remote system Value Definition Up to 21 alphanumeric characters Specifies the name of the remote system Version 2 type transfer device typically a printer receiving the report Up to 8 alphanumeric characters Version 1 type transfer Important Version does not refer to the release number of Unicenter CA XCOM Data Transport Notes The value of the parameter corresponds to a printer ID when the report is sent to an AS 400 For AS 400 the print destination name can be a fully qualified printer name The Menu Interface TSO ISPF Panels 2 53 Send Report To Another System Screen Report Title Copies Form Type 2 54 User Gu
112. valid start time specification for 1 a m the correct specification in this case is 0100 Similarly you cannot specify 5 to indicate that a transfer is to start 5 minutes from now instead you must specify two digits 05 as indicated by the format mm Default Current time The Menu Interface TSO ISPF Panels 2 103 File Transfer Scheduling Information Screen Selection Priority Hold 2 104 User Guide Specifies scheduling selection priority for the file transfer Value Definition 1 to 255 Specifies scheduling selection priority for the file transfer One is the lowest priority Notes Do not confuse this parameter with Execution Priority which applies after the file transfer has begun executing In situations where multiple file transfer requests are eligible for initiation that is they are past their start date time those with higher selection priorities are scheduled first Default 16 Prevents a queued transfer from executing until explicitly released by a Menu Interface SELECT or operator console RELEASE command both discussed later Value Definition Y Hold a queued transfer until released N Do not hold a queued transfer Default N Age File Transfer Scheduling Information Screen Overrides the Unicenter CA XCOM Data Transport default purging interval which is the number of days this request can remain on the Unicenter CA XCOM Data Transport queue before being purged Value Defini
113. valid value for this remote computer If it is not the print job fails Avoid this by defining this parameter with a value of null binary zero space or A Default A 3 62 User Guide CONTROL COPY or COPIES DEST SYSINO1 Parameters Indicates the printer carriage control codes present in the data stream Value Definition ASA ASA standard carriage control codes are used MACHINE Specific hardware dependent codes are used NONE No carriage control codes are used Default NONE Indicates the number of report copies printed Value Definition 0 to 255 Specifies the number of report copies to print Default 1 Indicates the printer or other device on the remote system receiving the report Value Definition Up to 21 characters Specifies the printer or device on the remote system Version 2 type receiving the report transfers only Up to 8 characters Version 1 type transfers only Notes The DEST parameter can contain a fully qualified printer filename when the report is sent to an AS 400 The actual number of bytes allowed for this parameter is dependent on the remote system Default System default printer The Batch Interface 3 63 SYSINO1 Parameters DISP FCB FORM 3 64 User Guide Determines whether to keep or delete the report file after printing on the remote system This value is ignored when the remote system is an IBM mainframe Value Definition KEEP Keep the report file after it
114. 0 500 LKEDTOP2 EXEC PGM IEWL COND 4 LT ASMTOP2 PARM XREF LET LIST NCAL AC 1 NORENT NOREUS NOTEST NOREFR SYSPRINT DD SYSUT1 DD SYSLMOD DD SYSLIN DD DD ENTRY XCOMTOP2 SYSOUT UNIT SYSALLDA SPACE 1024 500 20 DSN XCOM RVRMP LOAD DISP SHR DSN amp amp OBJSET DISP OLD DELETE XCOMTOP2 R Sample JCL for Reassembling and Link Editing XCOMACF2 Member ASMACF2U Sample JCL for Reassembling and Link Editing XCOMACF2 Member 20 This member contains sample JCL for reassembling and link editing the XCOMACE2 user security exit found on the distribution tape see CALCINBOSAM ASMACEF2U Assembly is required JOBNAME JOB ACCOUNTING INSTALLATION THIS JCL ASSEMBLES THE XCOMACF2 USER SECURITY EXIT FOR UID 1 ALTER JOBCARD TO CONFORM TO INSTALLATION STANDARDS 2 ENSURE UID IS CODED ON SYSPARM ASSEMBLER PARM 3 CHANGE SYSLIB TO POINT TO XCOM CINBOMAC 4 CHANGE SYSLIB TO POINT TO ACF2 MACRO LIBRARY 5 CHANGE SYSIN TO POINT TO XCOM CINBOSAM 6 CHANGE SYSLMOD TO POINT TO XCOM LOAD LIBRARY 7 CHANGE ACF2LIB TO POINT TO YOUR ACF2 LIBRARY Jf ASM EXEC PGM ASMA90 PARM SYSPARM UID OBJECT NODECK XREF SHORT NORENT SYSLIB DD DSN CAI CINBOMAC DISP SHR DD DSN YOUR ACF2 MACLIB DISP SHR DD DSN SYS1 MACLIB DISP SHR
115. 2 102 Parameter Fields 2 2 222 22 2 4 42 4 2 4 0 sean ba eb eee eee 2 103 Member Selection 486 2 2 107 Unicenter CA XCOM Data Transport Operator 1 2 109 Selecting a Display Option 24 2 2 109 Modifying the Filtering Options 2 110 Parameter Fields S500 AILES 2 110 Parametersstese ae eee ens 2 111 Unicenter CA XCOM Data Transport Transfer Request Display Screen 2 114 Sorting Transfer Request 2 115 Locatimg a 5246416 Re RE Rte dene deg rm qq qq u bae pd EE 2 115 Using the LOCATE Command euo q away ewe qu queue eua quede dud 2 116 iv User Guide Unprotected Control 6 2 2 2 2 117 Selection Commands 2529599 podus uu qua adu neue Mews V aW AUAM wah quan aM Rund a ba Nau gd 2 117 Protected Display Fields Ad dA Led dd edd Med ae 2 118 btatus Fields v u eee dodge o datu wa dire aud a uaa ud du odd dai eire 2 118 Detailed File Transfer Display IURE date isis P eb thes 2 120 Common Section Inform
116. 2 Undefined R13 Address of register save area R14 Return address R15 Entry point address The following registers are available at exit Register Description RO to R14 Undefined R15 Return code The only valid return code is 0 for a normal return The following is a sample program using this exit CAI CINBOSAM XCOMEX08 User Exit 9 Purpose User Exit 9 This exit point allows execution of a user developed exit routine that creates and processes its own Unicenter CA XCOM Data Transport commands The exit is activated by means of the EXIT operator command for example F XCOM EXIT userdata The supplied data up to eight bytes is then passed to the XCOMEXO09 routine where the user can perform any pertinent processing This exit can be used to control and alter the functionality of the other Unicenter CA XCOM Data Transport exits Module Name and Entry Point How to Enable Calling Module Entry Method Required DSECT The module name and entry point for this exit is XCOMEX09 Specify 09 in the Default Options Table to enable this exit The module XCOMXFER calls this exit This exit is a branch entry EXO9PLST is the required DSECT Addressing Mode at Entry The addressing mode at entry is 31 User Exits 0 19 User Exit 9 Registers at Entry Registers at Exit Valid Return Code Sample Program D 20 User Guide The following registers are available at entry Register Descripti
117. 3 BUFNI 3 FILSTAT ENABLED OPENED LSRPOOL NONE gt UPDATE IF NECESSARY RECFORM VARIABLE BLOCKED gt lt gt lt gt x gt x gt x gt x gt x SERVREQ READ ADD UPDATE BROWSE DELETE X STRNO 2 ed DSN XCOM XCOMDFLT VS DISP SHR gt OPTIONAL PARAMETER gt OPTIONAL PARAMETER C 38 User Guide Sample XCOMPCT Sample XCOMPCT This member contains the CICS PCT entries to run the Unicenter CA XCOM Data Transport CICS MVS interface If you create the PCT entries through the COPYCSD step which copies directly from the Unicenter CA XCOM Data Transport provided CSD to the user CSD this member is not required If you do not use the COPYCSD step you must copy these entries into the CICS PCT and assemble the PCT before Unicenter CA XCOM Data Transport can be used CICS PCT ENTRIES XCOM TRANSID FOR ALL XCOM FUNCTIONS T XCON OPTIONAL TRANSID FOR ALL XCOM FUNCTIONS XNTF TRANSID TO HANDLE ALL CICS NOTIFIES DFHPCT TRANSID XCOM PROGRAM XCICPRIM DTIMOUT 30 SPURGE YES TPURGE YES TRANSEC 01 TRMPRTY 100 TWASIZE 0 DFHPCT
118. 3I XCF REQ READ RC 00000000 REASON 00000000 LIST 0000 ENTRY XCOMPLEX QA XCOMM10221 LOCATING SERVER ENTRY IN LIST 0000 Starting the Unicenter CA XCOM Data Transport XCOMPLEX Worker Server XCOMM1026I UPDATING MASTER ENTRY IN LIST 0000 XCOMM1013I XCF REQ WRITE RC 00000000 REASON 00000000 LIST 0000 ENTRY XCOMPLEX_QA XCOMM1028I ADDING SERVER ENTRY FOR NODE XCPT WHICH IS USING LIST 0002 XCOMM1013I XCF REQ LOCK SET RC 00000000 REASON 00000000 LIST 0002 XCOMM1013I XCF REQ WRITE RC 00000000 REASON 00000000 LIST 0000 ENTRY XCOMM1055I CLEARING LIST 0063 FOR USE BY NODE XCOMM10131 XCF REQ DELETE MULT RC 00000000 REASON 00000000 LIST 0063 XCOMM1013I XCF REQ MONITOR LIST RC 00000000 REASON 00000000 LIST 0063 XCOMM10131 XCF REQ LOCK RESET RC 00000000 REASON 00000000 LIST 0002 XCOMMO719I SESSION ESTABLISHED WITH PLU XCOMMVS4 MODE SNASVCMG CID 04000061 DEST XCOMMVS4 SRUSIZE 00256 RRUSIZE 00256 06181 REMOTE CNOS REQUEST PROCESSED SUCCESSFULLY 04511 XCOMMVS4 NOW CONNECTED TO XCOMPLEX Admin Server XCPT XCOMMO719I SESSION ESTABLISHED WITH PLU XCPV MODE SNASVCMG CID 3800000E DEST XCOMPV SRUSIZE 00256 RRUSIZE 00256 06181 REMOTE CNOS REQUEST PROCESSED SUCCESSFULLY 04511 XCOMPV NOW CONNECTED TO XCOMPLEX Admin Server XCPT Starting the Unicenter CA XCOM Data Transport XCOMPLEX Worker Server Normally the XCOMPLEX Admin Server is brought up first then the XCOMPLEX Worker
119. 46 44504080548 46508eb0504G06 9 25 IRESHICHONS PR Nm 9 25 Mandows 98 iioteb e i i pbi bei eiie bei eiie bildete bei Tie bei Libet 9 26 Naming Conventions cues 2 uen uuu ue ea mes d n au RES 9 26 US SE 9 27 Contents ix Windows NT 2000 and XP 9 28 Naming Conventions u u quaa ua vela atas uaa iau agua Nuda Velauud auae ada we 9 28 Types of Piles Supported acciccedacesededetaiddndeda MARE IRURE ERE RIA PROS 9 29 Additional Features sxe comet oe boe dieat deed ee dedito dudit dedu 9 30 Destination Printer 9 31 uo Eu 9 32 Appendix About SNA Logical Units Partsof a 2222222 22 Ree RR o Rees Rene PPE ee eee RM RES A 1 ensi SE E A 1 Logical and Physical Network Components A 1 cci WEM NN s a t a spin sinis m A 2 2 Logical 06 EEEE EE EEE EEE 3 IBM s Strategie 0 IP A 3 LUSTY POS pU A 3 Independent Logical Units ILUS MARE PR RISE PER
120. 5 SSNDPAC 5 Sample XCOMTABL Table Member XCOMTABL LOGON MODE TABLE ENTRY NAME FUNCTION MANAGER PROFILE TRANSMISSION SERVICES PROFILE PRIMARY LOGICAL UNIT PROTOCOL SECONDARY LOGICAL UNIT PROTOCOL COMMON LOGICAL UNIT PROTOCOL RUSIZE SEC PRI 512 512 PRIMARY SEND PACING COUNT SECONDARY RECEIVE PACING COUNT SECONDARY SEND PACING COUNT PSERVIC X 060200000000000000002C00 PRESENTATION SRVCS XCOM256 MODEENT LOGMODE XCOM256 FMPROF X 13 TSPROF X 07 PRIPROT X BO SECPROT X BO COMPROT X 50B1 RUSIZES X 8585 PSNDPAC 5 SRCVPAC 5 SSNDPAC 5 LOGON MODE TABLE ENTRY NAME FUNCTION MANAGER PROFILE TRANSMISSION SERVICES PROFILE PRIMARY LOGICAL UNIT PROTOCOL SECONDARY LOGICAL UNIT PROTOCOL COMMON LOGICAL UNIT PROTOCOL RUSIZE SEC PRI 256 256 PRIMARY SEND PACING COUNT SECONDARY RECEIVE PACING COUNT SECONDARY SEND PACING COUNT PSERVIC X 060200000000000000002C00 PRESENTATION SRVCS XCOM512 MODEENT LOGMODE XCOM512 FMPROF X 13 TSPROF X 07 PRIPROT X BO SECPROT X BO COMPROT X 50B1 RUSIZES X 8686 PSNDPAC 5 SRCVPAC 5 SSNDPAC 5 LOGON MODE TABLE ENTRY NAME FUNCTION MANAGER PROFILE TRANSMISSION SERVICES PROFILE PRIMARY LOGICAL UNIT PROTOCOL SECONDARY LOGICAL UNIT PROTOCOL COMMON LOGICAL UNIT PROTOCOL RUSIZE SEC PRI 512 512 PRIMARY SEND PACING COUNT SECONDARY RECEIVE PACING COUNT SECONDARY SEND PACING COUNT PSERVIC X 060200000000000000002C00 PRESENTATION SRVCS
121. 5 RFIND 6 F7 UP F8 DOWN F9 SWAP FlO0 Language 11 1 F12 Alloc The Menu Interface TSO ISPF Panels 2 101 File Transfer Scheduling Information Screen Parameter Fields The parameter fields of the File Transfer Scheduling Information screen are described in the following Start Date Specifies the date the transfer is to begin The start date can be defined in absolute or relative terms m define a start date in absolute terms enter a numeric value in each of the three fields labeled Day Month and Year as follows Field Value Day 1 to 31 a day of the month Month 14012 month of the year interpreted according to the following chart 1 January 2 February 3 March 4 April 5 6 June 7 July 8 August 9 September 10 October 11 November 12 December Year nnnn a 4 digit designation for a year m define a start date in relative terms enter a number in the range 1 999 in the field labeled Number of days from today The number entered in this field indicates that the transfer is to start in that many days from today the current date For example if 1 is entered in this field the transfer will start one day from today or tomorrow Entering 7 in this field means that the transfer is to start seven days or one week from now Default Current date 2 102 User Guide Start Time File Transfer Scheduling Information Screen Specifies the time the transfer is
122. A1SZ95 XCOM R223 SAMPLIB ASMACF2U LE C XCOMDATA ASMACF2U SAM FIL DA1SZ95I 1616 DA1SZ95 LOCAL m LU30107 LE DA1SZ95 XCOM R223 SAMPLIB ISR PRIM LE C XCOMDATA ISR PRIM SAM 2 SPLIT F3 End 8 DOWN F9 SWAP F4 RETURN F5 RFIND Fl0 Language F11 Hold 20040828 1413 COMPLT 20040828 1412 COMPLT 20040828 1411 COMPLT 20040828 1251 COMPLT F6 RCHANGE F12 Alloc Unicenter CA XCOM Data Transport Transfer Request Display Screen Sorting Transfer Request Information Initially transfer request information is displayed in order of transfer request numbers Req Num By using the SORT command the initial display can be sorted in several different ways The format of the SORT command is as follows SORT sort field where sort field represents one of the sort criteria listed and described in the following table the items in parentheses are valid abbreviations Sort Criterion Description DATE Start date LOCFILE LF LFILE Local file name REMOTE REMSYS RSYS Remote system REQNUM RNUM Request number REMFILE RF RFILE Remote file name TIME Start time USERID UID User ID XFERID XID Transfer ID For example to sort transfer request information by the remote file name one of the following commands needs to be entered in the COMMAND INPUT field of the Transfer Request Display screen SORT REMFILE SORT RF SORT RFILE Locating a Request A particular file transfer request may be located by using the s
123. AD S XCOMAD Many of the messages that are displayed when you start the XCOMPLEX Admin Servers are the same as when you start a stand alone server but the following example shows some of the additional messages you will see Note the message which indicates that an XCOMPLEX Worker Server has successfully connected to the XCOMPLEX Admin Server 09901 ACTUAL XCOMDFLT PARMS XCOMMO9911 XCOMPLEX XCOMPLEX QA 09911 WINNERS 000004 00081 XCPT ACB OPENED SUCCESSFULLY XCOMMO0091 COMPILED UNDER VTAM V5 R1 MO EXECUTING UNDER VTAM V6 R1 M2 5695 11701 120 XCOMM07631 DEFAULT TABLE XCPTDFBO LOADED GENERATED 08 19 02 AT 11 56 00271 ESTAE ROUTINE HAS BEEN ESTABLISHED 00561 UNICENTER R CA XCOM R r11 GEN LEVEL 0410 5 00 IS UP AND ACCEPTING LOGONS 00561 ON CPU 2064 SERIAL 240AA1 IN 31 BIT MODE MVS SP7 0 2 XCOMM1000I CROSS COUPLING FACILITY LISTENER TASK STARTING XCOMM1000I STARTING CROSS SYSTEM COUPLING FACILITY SERVICE TASK 05591 XCOMPU ENABLED SUCCESSFULLY 05591 XCOMPS ENABLED SUCCESSFULLY 05591 XCOMPV ENABLED SUCCESSFULLY 05591 XCOMMVS4 ENABLED SUCCESSFULLY XCOMM1019I XCF CONNECT 5 QA CONN XCPT 00000000 RSN 00000000 DISP OLD XCOMM1020I MAXIMUM SERVERS SUPPORTED 00000061 XCOMM10541 MAXIMUM LIST ENTRIES SUPPORTED 00001673 XCOMM10171 XCF READING MASTER ENTRY FROM LIST 0000 XCOMM101
124. ATIONS AS THE SYS1 DUMPNN DATASETS IN USE AT YOUR SITE ICICI ICI II IG CI I AF SYSMDUMP DD DSN amp PREFIX SYSMDUMP DISP SHR SYSTEM DUMP Sample Files 21 Sample XCOMLSR Sample XCOMLSR This sample shows the server using the parameters for the LSR feature see CAI CINBOSAM XCOMLSR XCOMLSR PROC PREFIX XCOM RBO HIGH LEVEL DATA SET NAME QUAL CA XCOM FOR MVS SERVER ADDRESS SPACE USING LSR FOR XCOMRRDS T MINIMUM REQUIREMENTS FOR RRDS BUFND HDUBND AND STRNO ARE SHOWN BELOW BUT YOU MAY INCREASE THESE VALUES IF YOUR REGION HAS THE STORAGE AVAILABLE CHANGE RRDS BUFND AND HDUBND TO MAXTASK 1 2 gt CHANGE RRDS STRNO TO MAXTASK 1 WHERE MAXTASK 150 SERVER EXEC PGM XCOMXFER TIME 1440 REGION 80M PARM ACBNAME XCOMAPPL OVERRIDE DFLT STEPLIB DD DSN CAI CAILIB DISP SHR LOAD MODULES DD DSN CEE SCEERUN DISP SHR IBM LE RUNTIME SYSTCPD DD DSN TCPIP TCPIP DATA DISP SHR IBM TCP IP XCOMCNTL DD DSN amp PREFIX XCOMCNTL DISP SHR CONTROL LIBR DSVXRRD
125. B n LZRW 3 is coded If an unknown compression type is requested the file transfer is rejected Default YES CONTINUE DFLTAB PARM Parameters Tells Unicenter CA XCOM Data Transport how to proceed if a processing error is encountered during multi transfer processing Value Definition YES Tells Unicenter CA XCOM Data Transport to start the next transfer in a multi transfer request If this request is resubmitted Unicenter CA XCOM Data Transport resumes from the initial transfer in the multi transfer request NO Tells Unicenter CA XCOM Data Transport not to start any remaining transfers in the multi transfer request If this request is resubmitted because of a VTAM error Unicenter CA XCOM Data Transport resumes with the failed transfer If a logic error occurred Unicenter CA XCOM Data Transport resumes with the next transfer Notes This parameter is used in conjunction with the SYSINO1 parameter NEWXFER Unicenter CA XCOM Data Transport can only continue a resumed transfer from the point of failure if the XCOMREST and XCOMGLOB DD statements have been correctly defined Otherwise it resumes at the beginning of the transfer Default YES Indicates the name of the default table to be loaded and used by the Unicenter CA XCOM Data Transport server Value Definition XCOMDFLT Specifies the default table XCOMDFLT XXXXXXXX Specifies the name of the default table other than XCOMDFLT This name can be up to 8 alphan
126. BDEF ISPPLIB ISPEXEC LIBDEF ISPMLIB ISPEXEC LIBDEF ISPTLIB ALTLIB RESET Note Substitute your library names for the ones in the sample The Menu Interface TSO ISPF Panels 2 1 Menu Hierarchy Menu Hierarchy Unicenter CA XCOM Data Transport be invoked through TSO ISPF using the Menu Interface or the Unicenter CA XCOM Data Transport CLIST Library CALCINBOSCL Through the facilities of TSO ISPF Dialog Manager Unicenter CA XCOM Data Transport provides a set of fill in the blank menu screens The hierarchy of the main Unicenter CA XCOM Data Transport screens is shown next Unicenter Data Transport Selection Menu Display and Control Receive Files Send Functions Send Files Jobs and Reports Member List Display Detailed Displays Default Values 2 2 User Guide Each time you access Unicenter CA XCOM Data Transport s ISPF dialog previously selected values are retrieved from your ISPF profile However in the interest of security and data integrity certain parameters such as the Remote System Password Local System Password Notify User on Local System and Create Add Replace fields are not retained Instead they are set to their default values or blanks in the case of passwords Override inappropriate values for the current transfer by typing in the correct values Note Parameters that cannot be set through a Unicenter CA XCOM Data Transport screen will be set t
127. BM TCP IP XCOMPRNT DD SYSOUT SYSPRINT DD SYSOUT SYSTERM DD SYSOUT TEBCOPY MSGS TCP IP MSGS TCP IP MSGS SYSINO1l DD TYPE SEND DROPSESS YES FILEOPT REPLACE CKPT 0 NEWXFER TYPE SEND DROPSESS YES Sample XCOMJOB Schedule JCL Member XCOM JOBS Sample XCOMJOB Schedule JCL Member XCOMJOBS This member contains a sample XCOMJOB Schedule JCL CAI CINBOSAM XCOMJOBS found on the distribution tape This illustrates for a TYPE SCHEDULE transfer 1 2 s by JOBNAME JOB ACCOUNTING NAME CLASS A MSGCLASS X STEPO1 EXEC PGM XCOMJOB PARM TYPE SCHEDULE ACBNAME XCOM STEPLIB DD DSN CAI CAILIB DISP SHR DD DSN CEE SCEERUN DISP SHR SYSTCPD DD DSN TCPIP TCPIP DATA DISP SHR XCOMGLOB DD DSN XCOM RBO GLOBAL DISP SHR XCOMREST DD DSN XCOM RBO RESTART DISP SHR XCOMCNTL DD DSN XCOM RBO XCOMCNTL DISP SHR SYSPRINT DD SYSOUT SYSINO1 DD TYPE SEND DROPSESS YES FILETYPE FILE FILEOPT REPLACE CKPT 0 NOTIFY S LFILE oo i 35 xx FILE Rd NEWXFER TYPE SEND DROPSESS YES FILETYPE FILE FILEOPT REPLACE CKPT 0 64 4 44454 ox ER WOME a ara FILE T PEN LOADLIB IBM LE RUNTIME IBM TCP IP TCP IP MESSAGES Sample Files 25 Sample XCOMJOB Schedule JCL through the XCOMPLEX Admin Serve
128. C 3 HISTOUT DD statement B 5 hold file transfer request 3 74 File Transfer Scheduling Information screen 2 105 printing Send Report screen 2 57 transfer not completed B 2 HOLD MODIFY command 6 26 SYSINOI parameter 3 38 HOLDCOUNT SYSIN01 parameter 3 75 HSTDSECT Assembler macro B 2 ID SYSINO1 parameter 3 38 IDESC PARM parameter 3 16 system parameter 6 16 IDMS transactions 5 2 IEBISAM conversion utility 7 7 ILU See independent logical units INACT status field 2 118 independent logical units A 4 initialization processing user exit D 17 INQ MODIFY command 6 27 Inquire sample JCL C 10 INOWAIT SYSINOT parameter 3 39 interdependent transfers See multiple transfers invoking menu interface 2 1 IP address 2 6 3 15 name 2 6 port 2 6 IPNAME PARM parameter 3 17 SYSINOI parameter 3 39 IPPORT PARM parameter 3 17 SYSINOI parameter 3 40 system parameter 3 17 IROUT PARM parameter 3 18 system parameter 6 16 ISAM data set support 7 7 ISPF Dialog Manager services 2 3 Japanese Character Set Support Screen 2 100 JCL See also samples for XCOMUTIL B 5 JES destination name 5 10 remote destination 5 6 spool scanning interval 6 17 JES2 additional information user exit D 4 DESTID name 5 10 JES3 additional information user exit D 6 CONSOLE statement 5 10 JESINTV system parameter 6 17 JOBLIB DD statement 3 6 JPNCNTL SYSINO1 parameter 3 40 JPNDATA
129. CA XCOM Data Transport r11 and above that support secure SSL TCP IP A secure SSL TCP IP transfer allows for the encryption of the transmitted data and adds a digital signature to the encryption of the transmitted data Chapter 9 Remote System Information This chapter contains information about important aspects of the operating systems supported by Unicenter CA XCOM Data Transport that you should be aware of when performing transfers For more specific information about operating Unicenter CA XCOM Data Transport on a specific platform see the Unicenter CA XCOM Data Transport guides for that platform and the manufacturer s guides The following topics are covered for each platform as appropriate Naming conventions m Types of files supported m Additional features m Restrictions Remote System Information 9 1 AS 400 5 400 This section contains information about important aspects of the AS 400 operating system Naming Conventions Use the following format to specify an AS 400 file libraryname filename membername The following table describes the parts of an AS 400 file name Part Description libraryname The name of the library that holds the file filename The name of the file you wish to access Periods are allowed within the file name membername name of the member in the file If this component is omitted it defaults to the file name Types of Files Supported In addition to the sta
130. CF2 security exit C 33 JCL for reassembling and linkediting security exit C 30 JCL for reassembling and linkediting XCOMTOPS security exit C 31 logmode table C 12 maintaining history file C 6 mode table C 12 non queued transfer C 24 scheduled transfer JCL C 25 system administrator table C 17 TYPE EXECUTE transfer C 24 TYPE SCHEDULE transfer C 25 Unicenter CA XCOM Data Transport server definition C 21 Unicenter CA XCOM Data Transport startup JCL 21 VTAM application definition table C 10 XCDEFHLP C 34 XCOMENCR C 36 XCOMFCT C 38 XCOMJOB 3 3 XCOMMODE C 12 C 39 XCOMPPT C 40 41 save SYSINO1 Selection menu 2 12 scanning interval 6 17 scheduled start time alter priority with command line 6 8 Detailed File Transfer screen 2 121 Screens Extended Remote File Name Entry 2 99 File Allocation Information 2 42 File Transfer Display Select 2 109 File Transfer Scheduling Information 2 102 Member Selection List 2 107 Receive File From Another System 2 80 Selection menu 2 4 Send MVS File To Another System 2 15 Send Report to Another System 2 47 Submit Job 2 65 Transfer Request Display 2 114 using 2 1 scrolling 2 3 SEC system parameter 6 17 Secure Socket Layer 8 2 Secure Socket parameter 2 26 2 51 2 71 2 88 SECURE SCHEDULE parameter 3 22 SECURE SOCKET SYSIN01 parameter 3 50 security checking for TSO ISPF us
131. COM X XCOMREQ RELATE XCOM X XCOMHIST u SHR 2 3 NONUNIQUEKEY gt UPGRADE VOL VVVVVV RECSZ 20 300 gt CYLINDERS 1 1 KEYS 12 48 DATA NAME XCOM X XCOMREQ AIX DATA Sample Files 7 Sample XCOMUTIL Job Member XCOMUTIL C 8 User Guide DEF DEF DEF BIX BIX BIX BIX DEF DEF DEF I A CISZ 4096 NDEX NAME XCOM X XCOMREQ AIX INDEX CISZ 1024 IX NAME XCOM X XCOMRECP AIX RELATE XCOM X XCOMHIST SHR 2 3 NONUNIQUEKEY UPGRADE RECSZ 20 300 VOL VVVVVV CYLINDERS 1 1 KEYS 16 82 DATA NAME XCOM X XCOMRECP AIX DATA I A CISZ 4096 NDEX NAME XCOM X XCOMRECP AIX INDEX CISZ 1024 IX NAME XCOM X XCOMUSER AIX RELATE XCOM X XCOMHIST SHR 2 3 NONUNIQUEKEY UPGRADE RECSZ 20 300 VOL VVVVVV CYLINDERS 1 1 KEYS 20 28 DATA NAME XCOM X XCOMUSER AIX DATA I A CISZ 4096 NDEX NAME XCOM X XCOMUSER AIX INDEX CISZ 1024 IX NAME XCOM X XCOMIDNT AIX RELATE XCOM X XCOMHIST SHR 2 3 NONUNIQUEKEY UPGRADE RECSZ 20 300 VOL VVVVVV CYLINDERS 1 1 KEYS 18 98 DATA NAME XCOM X XCOMIDNT AIX DATA o o 0 CISZ 4096 NDEX NAME INDEX CISZ 1024 DS XCOM X XCOMHIST DS XCOM X XCOMREQ AIX IDS XCOM X XCOMHIST E DS XCOM X XCOMRECP AIX IDS XCOM X XCOMHIST E DS XCOM X XCOMUSER AIX
132. COM6LU1 XCOM6ABC or XCOM6001 The Remote Spooling Feature Process S YSOUT 5 11 PSOPREF Considerations PSOPREF Considerations The PSO interface uses catalogued data sets as a staging area This provides a more reliable means of transferring data than temporary data sets and also permits 5 transfers to be checkpointed and restarted if necessary The checkpoint count for PSO transfers PSOCKPT is set to 1000 by default This value can be defined in the Unicenter CA XCOM Data Transport default options table or in the destination members For PDSE program library transfers CKPT parameter is used to indicate the checkpoint value PSO data set names and temporary data sets created for PDSE program library transfers are controlled by the PSOPREF parameter This parameter specifies the high level qualifier used by Unicenter CA XCOM Data Transport when creating data sets Unicenter CA XCOM Data Transport then deletes these data sets after a file has been successfully transferred Format for PSO Data Set Names Data sets created by the PSO interface have the following data set name format pref ix Dyydad Thhmmss Xnnnnnnn The parts of the data set name are described below Part Description prefix Specifies the value specified for PSOPREF in the default table yyddd Specifies the Julian date when the data set is created hhmmss Specifies the time that the data set is created nnnnnnn Specifies the decimal number incremented for each
133. COMM07631 DEFAULT TABLE XCLSDF31 LOADED GENERATED 05 28 02 09 07 00271 ESTAE ROUTINE HAS BEEN ESTABLISHED XCOMMQ037I PSO SUBTASK ATTACHED SUCCESSFULLY 00561 UNICENTER R CA XCOM R r11 GEN LEVEL 0410 5 00 IS UP AND ACCEPTING LOGONS XCOMM0330I PRIMARY SUBSYSTEM IS JES2 0803 STARTING XCOM TCP IP LISTENER XCOMM07881 XCOM TCP IP LISTENER IS ACTIVE ON PORT 8044 IP ADDRESS After these messages have been displayed the Unicenter CA XCOM Data Transport server begins scanning through the destinations specified by the Unicenter CA XCOM Data Transport control library It is also ready to accept incoming requests from remote systems Operation and Control 6 1 Starting the Unicenter CA XCOM Data Transport XCOMPLEX Admin Server While it initializes Unicenter CA XCOM Data Transport issues one XCOMM0559I message for each member that is enabled as shown in the following example 05591 5400 ENABLED SUCCESSFULLY 05591 MVSPAR ENABLED SUCCESSFULLY Starting the Unicenter CA XCOM Data Transport XCOMPLEX Admin Server 6 2 User Guide Normally the XCOMPLEX Admin Server is brought up first then the XCOMPLEX Worker Servers although this is not required To start a Unicenter CA XCOM Data Transport XCOMPLEX Admin Server enter one of the following commands on the z OS console or any TSO ISPF or NETVIEW session where the user is authorized to invoke z OS system commands START XCOM
134. COMPLEX Admin Server Member XCOMJOXS C 26 Sample XCOMJOB Inquire Member XCOMJOBI C 27 Sample XCOMJOB Inquire JCL through the XCOMPLEX Admin Server Member XCOMJOXI 28 Sample JCL for Reassembling and Link Editing XCOMRACF Member ASMRACFU C 30 Sample JCL for Reassembling and Link Editing XCOMTOPS Member ASMTOPSU C 31 Sample JCL for Reassembling and Link Editing XCOMACF2 Member ASMACFT2U C 33 Sample 2 27 22 C 34 Sample DBEDBEET 5 d 35 Sample XCOMENCR JCL to Encrypt the SYSINO1 PASSWORD LPASS Parameters Member XCOMENCR EIN LIU E 36 Sample COPY CSD T a asa terrd a amaya saka sayas ede ee sh age d I dak PR tts C 37 Sample XCOMPC D S Hed ME UE E dmt Ete aUe HEN Dd dE C 38 Sample XCOMPCT 4 2 22422 2 22 2 C 39 Sample XCOMPPET Sues eee a m ose erg odd Sees oie C 40 Sample XCOMTGT tete bbb be de ob ee be o a te o eoa ue or ud C 41 Appendix D User Exits VSE ENIE T woy yaoa qaa dup dats D 2 rds AT rcx D 4 desi Pr D 6 Wser puquq baa Oke bat paqu l bh D 8 Contents xi User Exit
135. CR utility where SYSINO1 defines the input data stream and SYSOUTO I defines the output data stream with the encrypted password JOBNAME JOB ACCOUNTING ENCRYPT PASSWORD CLASS A MSGCLASS X RRR KR RK OK KK RK KKK KKK KKK SYSINO1 Input CA XCOM SYSINO1 file transfer parameters Can be DD PDS member or sequential file 5 500701 Output SYSINO1 parameters with encrypted values for LPASS and PASSWORD parameters Can be SYSOUT PDS member or sequential file XCOMENCR EXEC PGM XCOMENCR STEPLIB DD DSN CAI CAILIB DISP SHR SYSINO1 DD DSN XCOM RBO SYSINO1 DATA XFERPARM DISP SHR SYSOUTO1 DD DSN XCOM RBO SYSINO1 DATA ENCRYPTD DISP SHR User Guide C 36 Sample COPYCSD Sample COPYCSD This member contains the JCL that you may use during the installation process to copy the PCT PPT and TCT entries from the Unicenter CA XCOM Data Transport CSD file to the user CSD file Alternatively you can assemble the tables from the supplied PCT PPT and TCT tables JOBNAME JOB ACCOUNTING XCOMCSD CLASS A MSGCLASS X MSGLEVEL 1 1 NOTIFY TSOID X OOKOIOOIOK
136. D parameter Value Definition Up to 31 Specifies up to 31 characters representing the password alphanumeric associated with the local user ID parameter characters Notes This field does not display Notify User Volume Send MVS File To Another System Screen Specifies the local system user Unicenter CA XCOM Data Transport is to notify once the transfer completes Value Definition LOG LOG requests that the main operator on the local computer be notified If the local computer is a z OS system Unicenter CA XCOM Data Transport issues a WTO macro On an AS 400 or VAX system the operator console is notified user_id If any value but LOG is given Unicenter CA XCOM Data Transport interprets this as a specific user ID on the local system If that user is not logged on when the transfer completes the message is displayed the next time the user logs on Default LOG Specifies the name of the volume serial where the local data set may be found Value Definition Up to six Specifies up to six alphanumeric characters representing the alphanumeric of the volume serial where the local data set may be characters found Notes Used in conjunction with the local UNIT parameter The value must be the name of a volume currently mounted on this system or problems in allocation may occur Default Catalog information is used The Menu Interface TSO ISPF Panels 2 37 MVS Extended Tape Parameter Entry Unit
137. DARDS E n 2 ENSURE UID IS CODED ON SYSPARM ASSEMBLER PARM T 3 CHANGE SYSLIB TO POINT TO XCOM MACLIB 4 CHANGE SYSIN TO POINT TO XCOM CINBOSAM 2 5 CHANGE SYSLMOD TO POINT TO XCOM LOAD LIBRARY 7 85 HS CHANGE HISTORY m ID DATE DESCRIPTION N A 06 21 02 CREATION ASM EXEC 5 90 PARM SYSPARM UID OBJECT NODECK XREF SHORT NORENT SYSLIB DD DSN XCOM RVRMP MACLIB DISP SHR DD DSN SYS1 MACLIB DISP SHR DD DSN SYS1 AMODGEN DISP SHR DD DSN SYS1 MODGEN DISP SHR SYSUT1 DD UNIT SYSALLDA SPACE 1700 6000 100 SYSUT2 DD UNIT SYSALLDA SPACE 1700 6000 100 SYSUT3 DD UNIT SYSALLDA SPACE 1700 6000 100 SYSPRINT DD SYSOUT SYSIN DD DSN XCOM RVRMP CINBOSAM XCOMRACF DISP SHR SYSPUNCH DD DUMMY SYSOUT B SYSLIN DD DSN amp amp OBJSET DISP NEW PASS UNIT SYSALLDA SPACE 80 2000 500 LKED EXEC PGM IEWL COND 4 LT ASM PARM XREF LET LIST NCAL AC 1 NORENT NOREUS NOTEST NOREFR SYSPRINT DD SYSOUT SYSUT1 DD UNIT SYSALLDA SPACE 1024 500 20 SYSLMOD DD DSN XCOM RVRMP LOAD DISP SHR
138. Data Transport with the information necessary to submit a job from a z OS data set for execution on a remote system If the remote system is also a z OS system the job is submitted to an internal reader For non z OS systems the job is submitted to a comparable facility This data set must contain the control statements necessary to execute the job on the remote system for example CL for a DCL for a Digital Equipment Corp VAX computer or JCL for a z OS or VSE system Note The data set being sent must exist as a valid cataloged data set on the local system 04 10 26 Unicenter CA XCOM r11 5 00 TURKIO1 Submit Job To Another System Transfer ID Execution Priority Local File Name Local Tape Info File Seq Label Type Unit Count Vol Seq IP Name Addr 122 222 222 222 Port Secure Socket SSL NO Record Separators Y N Compression Mode EBCDIC Binary ASCII E B A E Pack Data Records N C L Truncate Record Transfer User Data Code Table System User Data Remote System Information Local System Information TURKIO1 Password Domain Notify User TURKIO1 1 3 End 11 Hold COMMAND gt F1 Help F2 SPLIT F3 End F4 RETURN F5 RFIND 6 F7 UP F8 DOWN F9 SWAP F10 Language 11 1 F12 Alloc The Menu Interface TSO ISPF Panels 2 65 Submit Job To Another System Screen Parameter Fields Transfer ID Execution Priority 2 66 User Guide The following
139. Definition Table Member YOU MUST CHANGE ALL OCCURENCES OF YOURTABL TO THE NAME OF THE APPROPRIATE MODE TABLE NAME FOR YOUR INSTALLATION THE FIRST APPLID XCOMAPPL WILL BE ATTACHED TO THE XCOM STARTED TASK ON THIS MVS SYSTEM IT WILL BE THE NAME USED BY ALL OTHER XCOM IMPLEMENTATIONS TO IDENTIFY THIS SYSTEM THEREFORE YOU MUST USE A DIFFERENT NAME IF YOU ARE RUNNING MORE THAN ONE VERSION OF XCOM WITHIN THIS VTAM ENVIRONMENT OTHERWISE WE HIGHLY RECOMMEND THAT YOU RETAIN THE ORIGINAL NAME IF YOU ARE ONLY RUNNING ONE VTAM VERSION OF THE SOFTWARE THIS WILL INSURE THAT THE SAMPLES ON THE OTHER SYSTEMS WILL MATCH IF YOU CHANGE THE NAME YOU MUST INFORM THOSE PERSONS RESPONSIBLE FOR THE IMPLEMENTATION OF XCOM ON THE OTHER SYSTEMS ADDITIONALLY YOU WILL HAVE TO CHANGE THE VALUE OF THE NETNAME KEYWORD IN THE XCOM MVS DEFAULT TABLE IF YOU CHANGE THE ACB NAME FOR THE FIRST APPLID THEN YOU WILL NEED TO ALTER THE VALUE OF THE ACBNAME KEYWORD ON THE DEFAULT TABLE TO MATCH THE SUBORDINATE APPLIDS XCOMOO THROUGH XCOMXX ARE USED FROM WITHIN THIS MVS SYSTEM TO DO DIRECT TYPE EXECUTE TRANSFERS TO OTHER COMPUTERS WITHIN YOUR SNAX COMNETWORK OR TO COMMUNICATE WITH THE XCOM STARTED TASK ON THIS SYSTEM YOU MUST BE CONSISTENT WITH THE PREFIX OF THE APPLID AND ACBNAMES USED FOR THESE THE PREFIX MAY BE FROM 4 TO 6 CHARACTERS LONG FOLLOWED BY THE 2 CHARACTER DIGIT IF YOU CHANGE THE PREFIX OF THE ACBNAME KEYWORDS HERE Y
140. E with Unicenter CA XCOM Data Transport m External writers give you more options when sending output to remote computers For example you can link remote host computers to particular external writers destination names are passed to the remote host which then equates them to a particular printer The following scenario illustrates how external writer support can be used Unicenter CA XCOM Data Transport is directed to transfer SYSOUT between two MVS hosts MVS1 and 52 Each has an external writer also MVS1 and MVS2 predefined by the other host computer in their respective Unicenter CA XCOM Data Transport Destination Tables but not to JES A problem might arise if a different JES destination RMT2 on the remote host other than the LOCAL predefined destination was needed Note The remote computer and a particular destination on it form what is called a compound destination Glace EE Process SYSOUT Enhancements In this case use both JES Destinations and External Writers Direct Unicenter CA XCOM Data Transport to scan for the external writer name only When Unicenter CA XCOM Data Transport finds work for the external writer MVS2 it sends it on to MVS2 while informing 52 that the destination name is 2 The output created by this JCL on 51 is then printed on RMT2 on MVS2 MVS1 eode Duae tures Ovens ees PSOTAB LU APPLMVS2 X WRITER MVS2 OUTPUT DD SYSOUT A
141. ER NAME XCOM X RRDS NUMBERED VOL VVVVVV RECORDS 1500 NO SECONDARY ALLOCATION ALLOWED BY XCOM RECSZ 2020 2020 FSPC O 0 x CISZ 2048 SHAREOPTIONS 2 3 DATA NAME XCOM X RRDS DATA REPRO IFILE INPUT ODS XCOM X RRDS C 2 User Guide Sample History File Creation JCL Member DEFHIST Sample History File Creation JCL Member DEFHIST The following is a copy of the sample History File Creation JCL found on the distribution tape CALCINBOSAM DEFHIST This JCL builds the Unicenter CA XCOM Data Transport History File and its associated indices and paths For history file maintenance use XCOMUTIL instead JOBNAME JOB ACCOUNTING XCOM INSTALLATION CLASS X MSGCLASS X MSGLEVEL 1 1 THIS JOB BUILDS THE XCOM HISTORY FILE ASSOCIATED INDICES 77 AND PATHS 1 DELETE THE OLD VSAM HISTORY FILE CLUSTER ALTERNATE INDICES AND PATHS 7 2 DEFINE THE BASE CLUSTER 77 3 THE SEED INITIALIZATION RECORD 75 BACK INTO THE BASE CLUSTER 4 BUILD ALTERNATE INDICES AND PATHS NOTE 1 REPLACE THE JOB CARD WITH ONE THAT IS VALID FOR YOUR SITE 77 2 CHANGE ALL OCCURENCES OF VVVVVV WITH A VALID DASD VOLSER NUMBER FOR VSAM FILES AT YOUR INSTALLATION 3 CHANGE ALL OCCURENCES OF XCOM X TO A VALID VSAM DATA SET PREFIX FOR YOUR INSTALLATION 4 RECSZ CHANGED FROM RECSZ 700 1200 TO RECSZ 1100 2020 J EXOOOOOOOK
142. ER THAT JUST HAPPENED THIS RECORD IS PRECEDED BY A 16 BYTE HEADER THAT CAN BE IGNORED ONCE YOU HAVE THIS INFORMATION YOU CAN DO WHATEVER YOUR APPLICATION REQUIRES MOVE 2000 TO MSG LENGTH EXEC CICS RECEIVE INTO IN MSG LENGTH MSG LENGTH END EXEC IF EIBCONF HIGH VALUES THEN EXEC CICS ISSUE CONFIRMATION END EXEC INSERT YOUR OWN LOGIC HERE EXIT END PROGRAM EXEC CICS RETURN END EXEC IT IS UNNECESSARY TO CODE AN EXEC CICS FREE SINCE THIS IS THE TARGET END OF THE CONVERSATION THE EXEC CICS RETURN WILL ACCOMPLISH WHAT IS NEEDED END OF SOURCE PROGRAM SAMP X X OX OX OX X X X X X Sample Files 23 Sample XCOMJOB Execute JCL Member XCOMJOBE Sample XCOMJOB Execute JCL Member XCOMJOBE C 24 User Guide This member contains a sample XCOMJOB Execute JCL CALCINBOSAM XCOMJOBE found on the distribution tape This illustrates JCL for a TYPE EXECUTE transfer JOBNAME JOB ACCOUNTING NAME CLASS A MSGCLASS X STEPO1 EXEC PGM XCOMJOB PARM TYPE EXECUTE ACBNAME XCOM STEPLIB DD DSN CAT CAILIB DISP SHR LOADLIB DD DISP SHR DSN CEE SCEERUN IBM C RUNTIME SYSTCPD DD DSN TCPIP TCPIP DATA DISP SHR XCOMGLOB DD DSN XCOM RBO GLOBAL DISP SHR XCOMREST DD DSN XCOM RBO RESTART DISP SHR XCOMCNTL DD DSN XCOM RBO XCOMCNTL DISP SHR XCOMPRNT DD REQUIRED IF PROGLIB YES IS PRESENT IN SYSINO1 I
143. ERS HAVE COMPLETED XCOMJOB ISSUES MESSAGE XCOMM657 FOR EACH INCOMPLETE TRANSFER XCOMJOB ISSUES A RETURN CODE WHICH MAY BE TESTED WITH COND ON SUBSEQUENT JOB STEPS STEPO3 EXEC PGM XCOMJOB PARM TYPE INQUIRE ACBNAME XCPT DFLTAB XCOMDFLT STCAPPL XCPT STEPLIB DD DSN CAT CAILIB DISP SHR LOADLIB DD DISP SHR DSN CEE SCEERUN RUNTIME SYSTCPD DD DSN TCPIP TCPIP DATA DISP SHR IBM TCP IP XCOMINQ DD DISP SHR DSN XCOM RBO XCOMINQ XCOMCNTL DD DISP SHR DSN XCOM RBO XCOMCNTL SYSPRINT DD SYSOUT TCP IP MSGS SYSTERM DD SYSOUT TCP IP MSGS SYSINO1l DD INQWAIT 000200 lt wait time Sample Files X X X X H 29 Sample JCL for Reassembling and Link Editing XCOMRACF Member ASMRACFU Sample JCL for Reassembling and Link Editing XCOMRACF Member ASMRACFU C 30 User Guide This member contains sample JCL for reassembling and link editing the user security exit found on the distribution tape see CALCINBOSAM ASMRACFU Assembling the XCOMRACT interface is optional JOBNAME JOB ACCOUNTING XCOM INSTALLATION CLASS X MSGCLASS X MSGLEVEL 1 1 VU THIS JCL ASSEMBLES THE XCOMRACF USER SECURITY EXIT FOR UID i 1 ALTER JOBCARD TO CONFORM TO INSTALLATION STAN
144. F Inserts a carriage return CR and line feed LF characters at the end of each record This is the packing type used for most Unicenter CA XCOM Data Transport platforms LENGTH Specifies that the records are to be packed into fixed size data transfer blocks Each record begins with a 2 byte long prefix that indicates the length of the record and determines how many records can be packed into a block The default block size is 2K but it can be increased to 31K by using the MAXPACK parameter in the Unicenter CA XCOM Data Transport Default Options Table or in the Unicenter CA XCOM Data Transport control library member When transferring a text file to a partner that supports record separators for example CRLF 0D0A on NT and LF 0A on UNIX record separators are inserted No separators are inserted in binary files transferred with PACK LENGTH NO No record packing is used Notes PACK LENGTH with MAXPACK 31744 should be selected when using Unicenter CA XCOM Data Transport over TCP IP If PACK LENGTH is coded then you must also code RECSEP NO Platforms that support PACK LENGTH are IBM s AS 400 UNIX based systems and z OS systems See the appropriate documentation for the platform to see if this value is supported For more information see Pack Data Records in the chapter The Menu Interface TSO ISPF Panels Default NO The Batch Interface 3 59 SYSINO1 Parameters RECSEP SPACE 3 60 User Guide Indicates
145. G ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMSJOB PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMMPRM PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMADSN PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMEDSN PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMOPER PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMODIS PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMOSDS PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCMHELP PGMLANG ASSEMBLER XCOM CICS PROGRAMS DFHPPT TYPE ENTRY PROGRAM XCICPRIM PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICSEND PGHLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICRF IL PGHLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICSFIL PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICSRPT PGHLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICS JOB PGHLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICMPRM PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICADSN PGHLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICEDSN PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICOPER PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICODIS PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICOSDS PGHLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICHELP PGHLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICSCHL PGHLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICCAPI PGMLANG ASSEMBLER DFHPPT TYPE ENTRY PROGRAM XCICNTFY PGHLANG ASSEMBLER Sample XCOMTCT Sample XCOMTCT This membe
146. IN 3 34 User Guide Specifies the one to eight character name of the data class to be use when allocating a new SMS managed data set Note This parameter applies only to mainframe SMS data sets Default None Identifies the Windows 2000 2003 or XP domain server used to validate the remote user ID and password Value Definition xxxxxxxxx Identifies the domain server used to validate the remote user ID and password The name can contain up to 15 characters Default None Notes Used with transfers to Windows 2000 2008 or XP only DROPSESS DSNTYPE SYSINO1 Parameters Indicates whether Unicenter CA XCOM Data Transport drops an LU to LU session at the conclusion of a scheduled file transfer Value Definition YES Indicates that Unicenter CA XCOM Data Transport drops the session NO Indicates that Unicenter CA XCOM Data Transport does not drop the session QEMPTY Indicates that Unicenter CA XCOM Data Transport is to process all the transfers to a particular LU in the request queue before dropping the session Default NO Notes Unicenter CA XCOM Data Transport for VAX and some Unicenter CA XCOM Data Transport for UNIX products do not support z OS initiated session establishment Therefore DROPSESS has no effect when the target of the transfer request is one of these platforms Specifies the data set definition Note This parameter applies only to mainframe SMS data sets Value Description LIBRARY Def
147. IP network Each computer in a TCP IP network is assigned at last one name which is resolved to a numeric address using either a translation file or an application known as the name server which is part of the Domain Name System function of the Application layer The notions of port and port number are extensions of the TCP IP address Once the TCP IP address has been used to deliver data to the desired computer in the network the port number is used to identify the process for which the data are intended By using ports and port numbers one computer can provide more than one service Unicenter CA XCOM Doata Transport uses a predefined port number but it can be changed if it interferes with existing application services Successful Send File Transfer Scenario This section contains a flow chart to illustrate a typical successful send file scenario Compare the steps below with the Send File Flowchart to follow a typical successful send file transfer 1 Thelocal Windows user invokes Unicenter CA XCOM Data Transport and requests a transfer 2 Unicenter CA XCOM Doata Transport verifies the information contained in the request Example Unicenter CA XCOM Data Transport checks to see if the local file exists on the local system 3 Unicenter CA XCOM Doata Transport establishes a connection with the remote system and sends along the header record to the remote system The header record contains transfer information regarding the request for
148. Job screen remote 2 76 2 79 PASSWORD 01 parameter 3 47 PCID See procedure correlation identifier pending delete transfer from pending queue 6 15 hold a pending transfer with command line 6 26 PF keys 2 3 POLCFRM define XCOMPLEX structure C 19 port 2 6 PRI system parameter 6 17 primary processing parameters 2 6 print 6 29 print class Send Report screen 2 57 PRINTOFF TSO command 5 1 priority sel exec Detailed File Transfer screen 2 121 procedure correlation identifier A 2 A 4 session ID A 2 process SYSOUT interface 6 17 process control user exit D 17 PROCESS XCOMUTIL parameter B 4 PROGLIB SYSINOT parameter 3 48 Program Library parameter 2 22 2 85 program sample Assembler 4 5 COBOL 4 3 programming language support 4 1 protected fields display 2 118 PSO sending reports with 5 3 PSOUNIT system parameter 6 17 PSOVOL system parameter 6 17 PSOWAIT destination table parameter 5 9 JES option 5 3 PU type A 5 purge file transfer request 3 74 history file utility B 2 with command line 6 45 Q queue execution parameters 6 8 for execution Selection menu 2 9 purging interval for locally initiated transfer requests 6 16 for remotely initiated transfer requests 6 17 Receive File From Another System screen local system information 2 96 remote system information 2 92 Receive File screen 2 80 parameter fields 2 81 Receive Files Selection
149. K KK KK KKK STEP1 EXEC PGM IXCL1DSU STEPLIB DD DSN SYS1 MIGLIB DISP SHR SYSPRINT DD SYSOUT SYSIN DD DEFINEDS SYSPLEX PLEX26 DSN your primary sysplex dsn VOLSER xxxxxx MAXSYSTEM 4 CATALOG DATA TYPE SYSPLEX ITEM NAME GROUP 50 ITEM NAME GRS NUMBER 1 ITEM NAME MEMBER 120 DEFINEDS SYSPLEX PLEX26 DSN your alternat sysplex dsn VOLSER yyyyyy MAXSYSTEM 4 CATALOG DATA TYPE SYSPLEX ITEM NAME GROUP 50 ITEM NAME GRS NUMBER 1 ITEM NAME MEMBER 120 Sample POLCFRM Member POLCFRM Sample POLCFRM Member POLCFRM This sample JCL shows how to define an XCOMPLEX structure This JCL is found on the distribution tape see CAI CINBOSAM POLCFRM POLCFRM JOB 00000000 ACCOUNT CLASS A MSGCLASS X MSGLEVEL 1 1 IR STEP20 EXEC PGM IXCMIAPU SYSPRINT DD SYSOUT SYSABEND DD SYSOUT SYSIN DD DATA TYPE CFRM REPORT YES DEFINE POLICY NAME XE26 REPLACE YES CF CFCCXCOM TYPE SIMDEV MFG IBM PLANT EN SEQUENCE 0000CFCCXCOM 0 0 CPCID 00 DUMPSPACE 4000 STRUCTURE IXCLIST1 SIZE 3840 PREFLIST CFCCXCOM STRUCTURE NAME ISTGENERIC SIZE 3840 PREFLIST CFCCXCOM STRUCTURE NAME ISTMNPS SIZE 3840 PREFLIST CFCCXCOM REBUILDPERCENT 30 STRUCTURE NAME XCOMPLEX SIZE 3840 PREFLIST CFCCXCOM STRUCTURE NAME XCOMPLEX QA SIZE 3840 PREFLIST CFCCXCOM STRUCTURE NAME SYS
150. KIO1 Tape Y N TURKIO1 11 Hold 12 Alloc F5 RFIND F6 RCHANGE F12 Alloc Parameter Fields Transfer ID Execulion Priority Send MVS File To Another System Screen The parameter fields for the Send MVS File to Another System screen are described on the following pages Associates a descriptive identifier with this file transfer It complements the request number assigned by Unicenter CA XCOM Data Transport to every locally initiated transfer Value Definition xxxxxxxxxx Specifies up to ten alphanumeric or national characters identifying the file transfer Notes The Unicenter CA XCOM Data Transport transfer IDs form a sequence that starts with 001 and is incremented by 1 for each transfer Default Your TSO user ID uuuuuuu with a sequence number nnn appended that is uuuuuuunnn Specifies the execution priority for this request Value Definition 1 to 255 Specifies a priority to provide efficient scheduling in a busy transfer environment 1 is the lowest execution priority Notes When multiple Unicenter CA XCOM Data Transport transmissions are executing concurrently transfers with higher execution priorities receive preferential service In a busy Unicenter CA XCOM Data Transport environment unless you have compelling reasons for not doing so enhance processing efficiency by giving short file transfers a higher priority value than long running transmissions Default 16 The Menu Interface TSO IS
151. M 192 SNA YES SSL NONE SSLPORT 8045 START XCOMSTRT SURCHK NO SURCLS SWAIT 30 TCPIP YES TCPLUSEC TCP IP 0 5 55 15 ENABLE DISABLE DYNAM SESSION ACQUIREXXCO00440 WTO DESCRIPTOR CODES FOR INFO MSGS 000450 DEFAULT TYPE INQUIRE INQUIRY WAIT XXC000460 DEFAULT TCP IP TARGET PORT XXC000470 WTO ROUTING CODES FOR INFO MSGS XXC000490 JES SPOOL SCAN INTERVAL XXC000500 RESERVED FOR FUTURE USE XXC000510 XCOMJOB ACB NAME PREFIX XXC000520 SMS DATA CLASS FOR THE LOCAL SYSTEM 000200 SMS DATASET NAME TYPE FOR THE LOCAL 000200 ENABLE DISABLE LIBRARY NEGOTIATION 000530 SMS MGMT CLASS FOR THE LOCAL SYSTEM 000200 ENABLE DISABLE XCOM TRANSFER LOG XXC000540 SYSOUT CLASS FOR XCOM TRANSFER LOG 000550 JES DESTINATION FOR XCOM TRANSFER 106 000560 DEFAULT MODE NAME FOR DLOGMOD XCOM 000570 REQUIRE LOGON TO USE LOGICAL UNIT XXC000580 DEFAULT NUMBER OF CONTENTION LOSERS 000590 SMS STOR CLASS FOR THE LOCAL SYSTEM 000200 ENABLE DISABLE LU ACCESS SECURITY XXC000600 ENABLE DISABLE 0864 SENSE CODE 000610 MAXIMUM NUMBER OF ACTIVE DELETE REQS 000620 MAXIMUM NUMBER OF ACTIVE LOCAL RQSTS 000630 MAXIMUM RECORD PACKING SIZE XXC000640 MAXIMUM NUMBER OF ACTIVE REMOTE RQSTSXXCO00650 MAXIMUM REPORT BLOCKSIZE XXC000660 MAXIMUM NUMBER OF ACTIVATE RQSTS XXC000670 FORMAT TO BE USED FOR XCOM MESSAGES 000680 PERMIT PROHIBIT MASTER CATALOG UPDATEXXC
152. M Data Transport to display all file transfers whose transfer IDs XID begin with the three characters BOY for example BOYCOTT BOYD BOYSCOUT and so on Unicenter CA XCOM Data Transport Transfer Request Display Screen Unprotected Control Fields Many of the fields on the Unicenter CA XCOM Data Transport Transfer Request Display screen are solely informational and cannot be altered that is they are protected However some fields are unprotected and allow you to change processing parameters for a file transfer Note Modifications are only allowed when listing transfers for an individual server and not when listing transfers for all XCOMPLEX Worker Servers connect to an XCOMPLEX Admin Server The unprotected fields are as follows m selection command m Prty SL scheduling priority m Prty EX execution priority m Start Time m Start Date To change the current values in control fields type over them Selection Commands Listed below are Unicenter CA XCOM Data Transport s selection commands To use a selection command enter it in the column labeled S next to a transfer request number REQ NUM and then press ENTER Command Definition Displays detailed information about a file transfer Displays detailed information about a file transfer Cancels a file transfer Holds a file transfer Releases a file transfer Suspends a file transfer Resumes a file transfer The Menu Interface
153. M X LOAD DISP SHR SYSPRINT DD SYSOUT HISTIN DD DSN 8 amp amp HSTSAV DISP OLD DELETE HISTOUT DD DSN amp amp HSTNEW UNIT SYSALLDA SPACE CYL 2 2 DISP NEW PASS SYSIN DD PROCESS HISTORY AGE X STEP3 EXEC PGM IDCAMS COND 4 LT CHANGED SYSPRINT DD SYSOUT SYSIN DD DELETE XCOM X XCOMHIST PURGE CLUSTER C 6 User Guide Sample XCOMUTIL Job Member XCOMUTIL 74 STEPA EXEC PGM IDCAMS COND 4 LT CHANGED SYSPRINT DD SYSOUT SYSIN DD DEF CLUSTER NAME XCOM X XCOMHIST KEYS 12 0 VOL VVVVVV CYLINDERS 5 2 RECSZ 1100 2020 5 0 0 SHAREOPTIONS 2 3 E DATA NAME XCOM X CISZ 4096 INDEX NAME XCOM X XCOMHIST INDEX CISZ 1024 gF H E E CHANGED 5 IF NO HISTORY RECORDS SLECTED PLACE A SEED INTO THE VSAM FILE CHANGED MR NNNM MEME CHANGED STEPS EXEC PGM IEBDG COND 4 NE CHANGED SYSPRINT DD SYSOUT OUTPUT DD DSN amp amp HSTNEW DISP OLD DCB LRECL 120 CHANGED SYSIN DD DSD OUTPUT OUTPUT CREATE QUANTITY 1 FILL X 00 STEP6 EXEC PGM IDCAMS COND 4 LT CHANGED SYSPRINT DD SYSOUT INPUT DD DSN amp amp HSTNEW DISP OLD CHANGED OUTPUT DD DSN XCOM X XCOMHIST DISP OLD SYSIN DD REPRO IFILE INPUT OFILE OUTPUT STEP7 EXEC PGM IDCAMS SYSPRINT DD SYSOUT SYSIN DD DEF AIX NAME X
154. MUM SERVERS SUPPORTED 00000061 XCOMM10541 MAXIMUM LIST ENTRIES SUPPORTED 00001673 XCOMM10171 XCF READING MASTER ENTRY FROM LIST 0000 XCOMM1013I XCF REQ READ RC 00000000 REASON 00000000 LIST 0000 ENTRY XCOMPLEX QA XCOMM10221 LOCATING SERVER ENTRY IN LIST 0000 XCOMM1026I UPDATING MASTER ENTRY IN LIST 0000 XCOMM1013I XCF REQ WRITE RC 00000000 REASON 00000000 LIST 0000 ENTRY XCOMPLEX_QA XCOMM1028I ADDING SERVER ENTRY FOR NODE XCPS WHICH IS USING LIST 0005 XCOMM1013I XCF REQ LOCK SET RC 00000000 REASON 00000000 LIST 0005 1013 XCF REQ WRITE RC 00000000 REASON 00000000 LIST 0000 ENTRY XCOMM1013I XCF REQ MONITOR LIST RC 00000000 REASON 00000000 LIST 0005 XCOMM10131 XCF REQ LOCK RESET RC 00000000 REASON 00000000 LIST 0005 XCOMM1005I XCOMPLEX SERVICES ENABLED FOR NODE XCPS 07881 XCOM TCP IP LISTENER ACTIVE ON PORT 8046 IP ADDRESS XCOMM1000I CROSS COUPLING FACILITY LISTENER TASK STARTING Using the Unicenter CA XCOM Data Transport MODIFY Commands The Unicenter CA XCOM Data Transport MODIFY commands allow users to interact with Unicenter CA XCOM Data Transport without logging on to ISPF and using the menu interface These commands use the same operating system facilities as the regular z OS MODIFY commands Most MODIFY commands can be used within the XCOMPLEX or in stand alone environments The MODIFY commands DUMPXCF NOXTRACE STAT XRSHOW XSHOW and XTRACE are intended for the XCOMPLEX environments onl
155. NA LU Name XCOM Group Name or XCOM List Name Login User Name Queue for Execution Y N Execute immediately APPLID of the CA XCOM Server CA XCOM Default Member Name XCOMCNTL Data Set Name Save SYSINO1 in DS Name Only Save SYSINO1 Y N PFK 1 Help 3 End C 2002 COMPUTER ASSOCIATES INC 1 1 F2 SPLIT F3 End F4 RETURN F5 RFIND F6 RCHANGE F7 UP F8 DOWN F9 SWAP FlO Language F11 Hold F12 Alloc 2 4 User Guide The Primary Option Menu Selection Menu Options The options for the Primary Option Menu are described in the table below Option Definition 1 Send Files Reports Jobs Used for sending a file report or job to a remote system 2 Receive Files Used for receiving a file from a remote system 3 XCOM Operator Control Used to display information about or to alter certain parameters pertaining to all pending in progress or completed transfers on a particular Unicenter CA XCOM Data Transport server Unicenter CA XCOM Data Transport Operator Control may also be used to change a transfer s status In a Coupling Facility environment this panel can also be used to display information about pending active and completed transfers for all Unicenter CA XCOM Data Transport XCOMPLEX Worker Servers connected to an XCOMPLEX Admin Server Changes cannot be made to this list of transfers changes can only be made when looking at a list of transfers for an individual XCOMPLEX Worker Server The Menu In
156. NAME XCOM04 VPACING 5 DLOGMOD XCOMMODE XCOMO5 APPL AUTH NOPO ACQ VPACE MODETAB YOURTABL SONSCIP YES ACBNAME XCOMO5 VPACING 5 DLOGMOD XCOMMODE Sample Files cn Sample XCOMTABL Table Member XCOMTABL Sample XCOMTABL Table Member XCOMTABL The following is a copy of the sample XCOMTABL Table CALCINBOSAM XCOMTABL found on the distribution tape The table contains sample XCOMMODE entries 5 12 User Guide 2X X X OX X X X OX X OX X X X X X X X X X X X X X OX X X X X X X X X X X X X X OX X OX X X X X OX X X X Xo X CA XCOM MODE ENTRIES A NOTE ABOUT RU SIZE ONE OF THE ADVANTAGES OF USING CA XCOM IS THAT IT CAN USE LARGER RU SIZES IN A WAY THAT OTHER SOFTWARE CANNOT LARGER RU SIZES GENERALLY MEAN FASTER THROUGHPUT THE ONLY DIFFERENCE BETWEEN THE MODE ENTRIES LISTED BELOW IS IN THE RU SIZE YOU ONLY NEED ONE OF THE MODE ENTRIES BELOW BUT YOU MAY FEEL FREE TO ADD AS MANY AS YOU LIKE TO YOUR EXISTING MODE TABLES THE DEFAULT MODE ENTRY XCOMMODE IS SET TO HAVE A 4K RU WE HAVE FOUND THIS TO BE A GOOD SIZE TO START WITH AS IT DOES NOT INTERFERE WITH EXISTING SNA TRAFFIC AND BUFFER CONSTRAINTS YET IT IS FASTER THAN THE RU SIZES USED BY MOST INSTALLATIONS REGARDLESS OF THE RU SIZE SET IN THE MODE ENTRY HERE THE RU WILL BE NEGOTIATED DOWN TO
157. NOTIFY ALL is selected then NOTIFYNAME shown following must also be specified Default LOG 3 46 User Guide NOTIFYNAME PASSWORD SYSINO1 Parameters Identifies the entity on the local system that is to receive a notification of the completion of the transfer Value Definition xxxxxxxx Indicates the TP name under CICS the ROSCOE key or ALL in 1 user to be notified at the conclusion of a file transfer by the initiator of the request The notification receiver name can be up to eight alphanumeric characters long Notes This parameter must be used when NOTIFY CICS NOTIFY ROSCOE or NOTIFY ALL has been selected If you specify NOTIFY CICS you must also specify NOTIFYNAME cics acbname If you specify NOTIFY ROSCOE you must also specify NOTIFYNAME roscoe key If you specify NOTIFY ALL you must also specify NOTIFYNAME mailbox name Identifies the password for the user ID under whose set of resource access privileges Unicenter CA XCOM Data Transport is to execute on the remote system It should be the password known to the remote security system Value Definition Up to 31 Specifies up to 31 characters representing the user alphanumeric password that is to be used for Unicenter CA XCOM characters Data Transport execution on the remote system Notes This value is overwritten with a string of asterisks or xxx when it appears in any Unicenter CA XCOM Data Transport log To change the remote TSO pass
158. NT PSERVIC X 060200000000000000002C00 PRESENTATION SRVCS XCOM16K MODEENT LOGMODE XCOM16K FMPROF X 13 5 07 SECPROT X BO COMPROT X 50B1 RUSIZES X 8B8B PSNDPAC 5 SRCVPAC 5 SSNDPAC 5 LOGON MODE TABLE ENTRY NAME FUNCTION MANAGER PROFILE TRANSMISSION SERVICES PROFILE PRIMARY LOGICAL UNIT PROTOCOL SECONDARY LOGICAL UNIT PROTOCOL COMMON LOGICAL UNIT PROTOCOL RUSIZE SEC PRI 16K 8 X 2 11 PRIMARY SEND PACING COUNT SECONDARY RECEIVE PACING COUNT SECONDARY SEND PACING COUNT PSERVIC X 060200000000000000002C00 PRESENTATION SRVCS XCOM32K MODEENT LOGMODE XCOM32K FMPROF X 13 TSPROF X 07 PRIPROT X BO SECPROT X BO COMPROT X 50B1 RUSIZES X 8C8C PSNDPAC 5 SRCVPAC 5 SSNDPAC 5 LOGON MODE TABLE ENTRY NAME FUNCTION MANAGER PROFILE TRANSMISSION SERVICES PROFILE PRIMARY LOGICAL UNIT PROTOCOL SECONDARY LOGICAL UNIT PROTOCOL COMMON LOGICAL UNIT PROTOCOL RUSIZE SEC PRI 32K 8 X2 12 PRIMARY SEND PACING COUNT SECONDARY RECEIVE PACING COUNT SECONDARY SEND PACING COUNT PSERVIC X 060200000000000000002C00 PRESENTATION SRVCS SNASVCMG MODEENT LOGMODE SNASVCMG FMPROF X 13 TSPROF X 07 PRIPROT X BO SECPROT X BO COMPROT X DOB1 LOGON MODE TABLE ENTRY NAME FUNCTION MANAGER PROFILE TRANSMISSION SERVICES PROFILE PRIMARY LOGICAL UNIT PROTOCOL SECONDARY LOGICAL UNIT PROTOCOL COMMON LOGICAL UNIT PROTOCOL gt lt
159. O XCOMCNTL XCOMINQ DD DISP SHR DSN XCOM RBO XCOMINQ SYSINO1 DD TYPE SEND LU XCOMMJM2 FILETYPE FILE FILEOPT REPLACE LFILE XCOM28 FILE2 FILE XCOM28 FILE3 MORE JOB STEPS CAN BE INSERTED HERE p e THIS STEP USES XCOMJOB TYPE INQUIRE TO DETERMINE THE STATUS OF THE TRANSFER REQUESTS RECORDED IN THE XCOMINQ FILE XCOMJOB ISSUES MESSAGE XCOMM655 FOR EACH COMPLETED TRANSFER AND REMOVES THE TRANSFER NUMBER FROM THE XCOMINQ FILE ANY OF THE TRANSFERS SPECIFIED IN THE XCOMINQ FILE IS IS ACTIVE OR SUSPENDED XCOMJOB WAITS UNTIL IT COMPLETES OR IF THE TIME INTERVAL SPECIFIED BY INQWAIT ELAPSES BEFORE ALL TRANSFERS HAVE COMPLETED XCOMJOB ISSUES MESSAGE XCOMM657 FOR EACH INCOMPLETE TRANSFER XCOMJOB ISSUES A RETURN WHICH MAY BE TESTED WITH COND ON SUBSEQUENT JOB STEPS STEPO3 EXEC PGM XCOMJOB PARM TYPE INQUIRE ACBNAME XCOMM1 CONTINUE NO STCAPPL XCOMAPPL XCOMCNTL DD DISP SHR DSN XCOM RBO XCOMCNTL XCOMINQ DD DISP SHR DSN XCOM RBO XCOMINQ SYSINO1 DD INQWAIT 000200 lt wait time Sample Files 27 Sample XCOMJOB Inquire JCL through the XCOMPLEX Admin Server Member XCOMJOXI Sample XCOMJOB Inquire JCL through the XCOMPLEX Admin Server Member XCOMJOXI This member contains a sample XCOMJOB Inquire JCL through the XCOMPLEX Admin Server CAI CINBOSAM XCOMJOXT fo
160. O00690 NAME PASSED IN CINIT BIND VECTORS XXC000700 NO NETMASTER INTERFACE SUPPORT XXC000700 CICS TRAN TO START AT TRANSFER END 000710 MAXIMUM NUMBER OF RECORDS TO DISPLAY 000720 TYPE OF SECURITY FOR OPER FUNCTIONS 000730 PRIMARY ALLOC FOR DATASET CREATION 000740 CKPT COUNT DEFAULT 1000 IF OMITTED X PSO DATASET DISPOSITION X HIGH LEVEL PREFIX FOR PSO DATASETS 000750 ENABLE DISABLE EXIT5 FOR PSO INDIRECTXXCO00760 UNIT NAME FOR PSO DATASETS XXC000770 VOLUME SERIAL NUMBER FOR PSO DATASETSXXCO00780 ENABLE DISABLE DATASET PSWD SUPPORT 000790 RECEIVER ID FOR NETMASTER XXC000800 RESERVED FOR FUTURE USE XXC000800 AGE AT WHICH TO PURGE REMOTE REQUESTSXXCO00810 OF ROSCOE PROCEDURE FOR NOTIFY 000820 RESERVED FOR FUTURE USE XXC000830 SECONDARY ALLOC FOR DATASET 000850 TYPE OF SECURITY TO BE USED IP XFERS 000860 TYPE OF SECURITY TO BE USED XXC000860 SESSION ESTABLISHMENT RETRY LIMIT XXC000870 TCP SERVER LOCAL ADDRESS XXC000880 DEFAULT TCP IP SERVER PORT 000880 ENABLE DISABLE SMF RECORDING XXC000890 SMF RECORD NUMBER TO BE USED XXC000900 ENABLE DISABLE SNA TRANSFER XXC000900 ENABLE DISABLE SSL TRANSFER ONLY 000900 SSL PORT TO USE WITH SSL TRANSFERS 000900 NAME OF XCOMCNTL STARTUP MEMBER XXC000910 ENABLE DISABLE SURROGATE USER SUPPORTXXCO00920 RESOURCE CLASS FOR SURROGATE USER CHKXXCO00930 SESSION ESTABLISHMENT WAIT TIME LIMITXXCO00940 TCP IP SUPPO
161. OIOKOIOKOIOK IO S1 EXEC PGM IEBDG SYSPRINT DD SYSOUT OUTPUT DD DSN amp amp TEMP UNIT SYSALLDA SPACE TRK 1 DCB RECFM FB LRECL 1000 BLKSIZE 1000 DISP NEW PASS SYSIN DD DSD OUTPUT OUTPUT CREATE QUANTITY 1 FILL X 00 S21DCAMS EXEC PGM IDCAMS REGION 1024K SYSPRINT DD SYSOUT INPUT DD DSN amp amp TEMP DISP OLD SYSIN DD DELETE XCOM X XCOMHIST SET MAXCC 0 DEF CLUSTER NAME XCOM X XCOMHIST KEYS 12 0 VOL VVVVVV CYLINDERS 5 2 RECSZ 1100 2020 gt FSPC O 0 SHAREOPTIONS 2 3 DATA NAME XCOM X CISZ 4096 INDEX NAME XCOM X XCOMHIST INDEX CISZ 1024 REPRO IFILE INPUT ODS XCOM X XCOMHIST Sample Files 3 Sample History File Creation JCL Member DEFHIST C 4 User Guide DEF DEF DEF DEF BIX BIX BIX AIX XCOM X XCOMREQ RELATE XCOM X XCOMHIST SHR 2 3 NONUNIQUEKEY UPGRADE VOL VVVVVV RECSZ 20 300 CYLINDERS 1 1 5 12 48 DATA NAME XCOM X XCOMREQ AIX DATA CISZ 4096 INDEX NAME XCOM X XCOMREQ AIX INDEX CISZ 1024 AIX XCOM X XCOMRECP RELATE XCOM X XCOMHIST SHR 2 3 NONUNIQUEKEY UPGRADE RECSZ 20 300 VOL VVVVVV CYLINDERS 1 1 KEYS 16 82 DATA NAME XCOM X XCOMRECP AIX DA
162. OM Data Transport for z OS started task This entry sequence allows the user to determine whether the transfer should be queued for execution If the target LU must be tested for a TYPE SCHEDULE transfer the test must be deferred until the exit is called by XCOMXFER User Exit 5 The following table summarizes how the exit is given control EXEC PARM XCOMEXO5 Entry SECLUN Contents Sequence XCOMJOB TYPE EXECUTE XCOMJOB gt REMOTE LU OR IP XCOMFILE ADDRESSS hex XCOMEX05 XCOMJOB TYPE SCHEDULE XCOMJOB gt XCOMAPPL that is the XCOMFILE gt APPLID of the Unicenter XCOMEX05 CA XCOM Data Transport for z OS server XCOMXFER N A gt LU OR IP XCOMFILE ADDRESSS hex XCOMEX05 The CSAJOBF field in the CSA CSADSECT identifies which entry sequence XCOMJOB or XCOMXFER was used while the NSABATF field in the NSA NSADSECT identifies the transfer as being of type TYPE EXECUTE or TYPE SCHEDULE Field EQU Field Contents Description CSAJOBF CSAJOBJ Character J 5 entered via XCOMJOB CSAJOBX Character X XCOMEX05 entered via XCOMXFER NSABATF NSABATE Character E TYPE EXECUTE transfer NSABATS Character S TYPE SCHEDULE transfer Note CSADSECT and NSADSECT are distributed in Unicenter CA XCOM Data Transport s macro library Entry Method This exit is a branch entry Addressing Mode at Entry The addressing mode at entry is 31 User
163. OU MUST CHANGE THE JOBACB VALUE IN THE LOCAL XCOM DEFAULT TABLE xe X 0X 0X 0X EE KH x KE HE WE HAVE SELECTED THE MODE ENTRY NAME XCOMMODE TO MATCH THE MODE NAME USED BY THE SAMPLE CONFIGURATIONS IN OTHER IMPLEMENTATIONS OF XCOM WE STRONGLY SUGGEST THAT YOU KEEP THIS NAME YOU HAVE ANY QUESTIONS THIS TABLE IS EXPLAINED IN GREATER DETAIL IN THE ADMINISTRATOR GUIDE APPLXCOM VBUILD TYPE APPL XCOMAPPL APPL AUTH NOPO ACQ VPACE MODETAB YOURTABL SONSCIP YES ACBNAME XCOMAPPL VPACING 5 DLOGMOD XCOMMODE PARSESS YES XCOMOO APPL AUTH NOPO ACQ VPACE MODETAB YOURTABL SONSCIPZYES ACBNAME XCOMOO VPACING 5 DLOGMOD XCOMMODE XCOMO1 APPL AUTH NOPO ACQ VPACE MODETAB YOURTABL ONSCIPZYES ACBNAME XCOMO1 VPACING 5 DLOGMOD XCOMMODE XCOMO2 APPL AUTH NOPO ACQ VPACE MODETAB YOURTABL sd SONSCIP YES 0 2 VPACING 5 DLOGMOD XCOMMODE XCOMO3 APPL AUTH NOPO ACQ VPACE MODETAB YOURTABL SONSCIP YES VPACING 5 DLOGMOD XCOMMODE XCOMO4 APPL AUTH NOPO ACQ VPACE MODETAB YOURTABL SONSCIP YES ACB
164. P VS DATA UNIQUE INDEX NAME XCOM XCOMHELP VS INDEX UNIQUE REPRO IFILE DD1 ODS XCOM XCOMHELP VS Sample DEFDFLT Sample DEFDFLT This member contains JCL to define and populate the Unicenter CA XCOM Data Transport CICS MVS Default File XCOMDFLT JOBNAME JOB ACCOUNTING XCOM DFLT DEFINE CLASS A MSGCLASS X MSGLEVEL 1 1 NOTIFY TSOID XCOMCICI EXEC PGM XCICCICI STEPLIB DD DSN XCOM CICS RVRMP LOAD DISP SHR XCOMOUT DD DSN amp amp TEMP DISP NEW PASS 1 UNIT SYSDA XCOMIN DD SERVER APPLID XCOMAPPL OPER TRAN XCOM IDCAMS EXEC PGM IDCAMS SYSPRINT DD SYSOUT DD1 DD DSN amp amp TEMP DISP OLD DELETE SYSIN DD 4 DELETE AND REDEFINE THE XCOMCICS DEFAULT FILE 5 DEFINE CL NAME XCOM XCOMDFLT VS IXD REC 1000 RECSZ 80 1500 VOLUME FREESPACE 0 0 KEYS 8 0 SHR 2 DATA NAME XCOM XCOMDFLT VS DATA UNIQUE INDEX NAME XCOM XCOMDFLT VS INDEX UNIQUE REPRO IFILE DD1 ODS XCOM XCOMDFLT VS REPLACE Sample Files 35 Sample XCOMENCR JCL to Encrypt the SYSINO1 PASSWORD LPASS Parameters Member XCOMENCR Sample XCOMENCR JCL to Encrypt the SYSINO1 PASSWORD LPASS Parameters Member XCOMENCR This member contains a sample XCOMENCR JCL to encrypt the SYSINO1 PASSWORD LPASS parameters found on the distribution tape CALCINBOSAM XCOMENCR This illustrates the use of the XCOMEN
165. PF Panels 2 17 Send MVS File To Another System Screen Local File Name 2 18 User Guide Indicates the name of the local data set being transferred Required Value Definition Up to 56 Specifies up to 56 characters consisting of the following a pha umenie A 1 to 44 character data set name characters An optional member name enclosed in parentheses Optional single quotation marks apostrophes to enclose the data set The user s TSO profile prefix is inserted at the beginning of this entry unless the entry is enclosed in single apostrophes If the TSO profile is set to NOPREFIX nothing is inserted Notes Use an asterisk to send multiple members of a partitioned data set Specifying an asterisk for the member name will send all members of a PDS for example SURVEYS To send all members beginning with a specific prefix specify this prefix followed by an asterisk For example NAMES PDS AL requests that members AL ALEX and ALICE all be transferred The asterisk must be the last character before the right parentheses If no member name is entered for a partitioned data set a Member Selection List panel is displayed allowing the selection of one or more members for transfer For more information see Remote File Name and Member Selection List in this chapter Default The last data set name entered Send MVS File To Another System Screen Remote System Identification IP Name Addr SNA LU Name XCOM Group Name
166. PSO transfer For PDSE Program Library Transfers 5 12 User Guide Data sets created by the PSO interface for PDSE program library transfers have the following data set name format m prefix Jyyddd Thhmmss amp nnnnnnn for the initiating side m prefix Jyyddd Rhhmmss snnnnnnn for the receiving side PSOPREF Considerations The parts of the data set name are as follows Part Description prefix Specifies the value specified for PSOPREF in the default table yyddd Specifies the Julian date when the data set is created hhmmss Specifies the time that the data set is created nnnnnnn Specifies the request number for each PDSE program library transfer Determining the User Catalog for the Unicenter CA XCOM Data Transport PSO Interface The high level qualifier of the prefix specified in the PSOPREF parameter determines the system catalog in which the data sets created by Unicenter CA XCOM Data Transport s PSO interface are to be cataloged If a user catalog alias has not been created for this high level qualifier the data sets are cataloged in the system s master catalog Aside from being undesirable in most cases this requires MSTRCATU YES to be specified in the Unicenter CA XCOM Data Transport Default Options Table You can create a user catalog for the Unicenter CA XCOM Data Transport PSO interface data sets by using the DEFINE USERCATALOG command under TSO or the IDCAMS batch utility program Once this user catalog has been created
167. RSHOW command Operand Description nnnnnn Specifies the request number nnnnnn of the remotely initiated transfer about which detailed information is to be displayed destname Specifies the name of the destination whose remotely initiated transfers are to be displayed Any of the following items can be used as a destination name m SNALU name TCP IP name m TCP IP address Using the Unicenter CA XCOM Data Transport MODIFY Commands Note Entered without an operand RSHOW displays all remotely initiated transfer requests Notes The display provides information about m Requests that are active m Requests that were interrupted but are still eligible to be restarted for example requests that have not yet been completed purged or aged off the queue Important In large networks with a large number of queued transfers the output of this command can exhaust your WTO buffers Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name READ XCOM applsec RSHOW destname ownername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination involved in the transfer m ownername the user ID under whose security authorization the transfer is performed N
168. RT ENABLED XXC000950 SECURITY CALL TCP IP ADDRESS X DEFAULT TCP IP RECEIVE TIMEOUT VALUE X MAX OF IP SESSIONS PER PARTNER XXC000960 TCPSOCKD TCPSRCVB 64 TCPSSNDB 64 TCPSTACK TCPTBUF TCPTCHKF TCPTTIME TERL 32767 TIMEOUT 600 UNIT SYSALLDA USERD XCOMMVS USEROVR YES USERPRO NO VERL 255 VOL VTAMGNAM WINNERS 4 XCOM_CONFIG_SSL XCOMPLEX Sample XCOMADMT Table Member XCOMADMT TCPIP SOCK_DELAY TCPIP SOCK_RCV_BUF_SIZE TCPIP SOCK_SEND_BUF_SIZE JOB NAME OF TCPIP STACK TCPIP TXPI_BUF_SIZE TCPIP TXPI_SEND_CHECK_FREQ TCPIP TERM TIMEOUT TOTAL ERROR RETRY LIMIT DEFAULT TYPE EXECUTE TIMEOUT VALUE UNIT NAME FOR DATASET CREATION DEFAULT TRANSFER USER DATA ENABLE DISABLE USER ID OVERRIDES ENABLE DISABLE USER ID PROPAGATION VTAM ERROR RETRY LIMIT VOLUME FOR DATASET CREATION VTAM GENERIC ACBNAME XXC001060 XXC001060 XXC001060 XXC001060 XXC001060 XXC001060 001060 XXC000970 XXC000980 XXC000990 XXC001000 XXC001010 XXC001020 001030 001040 001070 DEFAULT NUMBER CONTENTION WINNERS 001050 NAME OF DATASET THAT HAS THE SSL CONFXXCO01080 X SYSTEM COUPLING STRUCTURE NAME 001080 Sample XCOMADMT Table Member XCOMADMT The following is a copy of the sample XCOMADMT Table found on the distribution tape CAI CINBOSAM XCOMADMIT P IR
169. S DD DISP SHR DSN amp PREFIX RRDS ACTIVE REQSTS XCOMRRDS DD SUBSYS BLSR DDNAME DSVXRRDS USAGE OF BLSR RMODE31 ALL BUFFERS ABOVE 16M BUFND 302 SET BUFND MAXTASK 1 2 STRNO 151 STRNO lt MAXTASK 1 gt DEFERW NO NO FOR INTEGRITY XCOMHIST DD DSN amp PREFIX XCOMHIST DISP SHR DONE REQUESTS XCOMREQ DD DSN amp PREFIX XCOMREQ PATH DISP SHR ACCESS PATH XCOMUSER DD DSN amp PREFIX XCOMUSER PATH DISP SHR ACCESS PATH XCOMIDNT DD DSN amp PREFIX XCOMIDNT PATH DISP SHR ACCESS PATH XCOMRECP DD DSN amp PREFIX XCOMRECP PATH DISP SHR ACCESS PATH SYSPRINT DD SYSOUT TCP IP MSGS THE FOLLOWING XCOMPRNT DD STATEMENT DEFINES THE SYSOUT FOR THE MESSAGES WHEN PDSE PROGRAM LIBRARIES ARE TRANSFERRED YOU MAY SET THIS TO DD DUMMY IF YOU DO NOT WISH TO SEE THESE MESSAGES XCOMPRNT DD SYSOUT EBCOPY MSGS THE FOLLOWING SYSMDUMP DD STATEMENT DEFINES A SYSTEM DUMP DATA SET THIS DATA SET SHOULD BE GIVEN THE SAME SPACE ALLOCATIONS AS THE SYS1 DUMPNN DATASETS IN USE AT YOUR SITE THE DCB CHARACTERISTICS OF THIS DATASE
170. SUCCESSFUL A26IXCOM TASK CURRENT LIMIT PERCENT TYPE COUNT MAX UTILIZED LOCAL 8 75 10 REMOTE 0 75 0 TASKS 8 150 5 2 HELD 9 SUSPENDED 9 zz REM SUSPND 2 a RETRY PEND 0 INACTIVE 9 26 5 CURRENT LIMIT PERCENT TYPE COUNT MAX UTILIZED LOCAL 2 25 8 0 25 0 TASKS 2 50 4 1 se HELD 0 SUSPENDED 9 gt REM SUSPND 9 RETRY PEND 9 INACTIVE 0 az A26UXCOM TASK CURRENT LIMIT PERCENT TYPE COUNT MAX UTILIZED LOCAL 7 50 14 REMOTE 0 50 0 TASKS 7 100 7 1 HELD 0 SUSPENDED 0 REM SUSPND 1 a RETRY PEND 0 INACTIVE 1 gt Operation and Control 6 41 Using the Unicenter CA XCOM Data Transport MODIFY Commands STOP Command Format 6 42 User Guide Stops Unicenter CA XCOM Data Transport F XCOM STOP IMMED The following table lists the various commands by which the Unicenter CA XCOM Data Transport server can be stopped and describes the circumstances under which each command is used Operand no operand IMMED Description When the STOP command is issued without an operand that is 5 it causes Unicenter CA XCOM Data Transport to stop as soon as all active transfers are completed F XCOM STOP IMMED causes Unicenter CA XCOM Data Transport to stop immediately and unconditionally that is even if transfers are in progress When
171. SYSIN REC WRITE SYSIN REC 004400 MOVE LFILE XCOM RB0 SAMPLIB XCSAMCOB TO SYSIN REC 004450 WRITE SYSIN REC 004500 MOVE CODE EBCDIC TO SYSIN REC WRITE SYSIN REC 004600 MOVE FILE C NMVSNTEMP TO SYSIN REC WRITE SYSIN REC 004700 CLOSE SYSIN FILE 004800 004900 KK K K k k K k k k k 005000 WE WILL CALL XCOMJOB HERE 005100 K X K K K K K X X K K X X KX X X K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K 005200 005300 CALL XCOM API USING XCOM PARM 005400 IF RETURN CODE NOT EQUAL ZEROS 005500 THEN DISPLAY TRANSFER FAILED 005600 ELSE DISPLAY TRANSFER SUCCESSFUL 005700 STOP RUN I LINK EDIT PROGRAM CR A A I LKED SYSLMOD DD DSN XCOM APF3 LINKLIB DISP SHR INCLUDE SYSLMOD XCOMJOB LKED SYSIN DD ENTRY SAMPCOB NAME SAMPCOB R IO EXECUTE PROGRAM J RRR RRR RK KK KK RK KKK KK KKK KKK KKK KKK RUN EXEC PGM SAMPCOB STEPLIB DD DSN XCOM APF3 LINKLIB DISP SHR SYSOUT DD
172. SYSINO1l DD TYPE SEND WU ss FILETYPE FILE FILEOPT REPLACE THIS STEP USES XCOMJOB TYPE SCHEDULE TO INITIATE A FILE TRANSFER SINCE THE SAME XCOMINQ FILE IS USED AS IN THE PREVIOUS STEP THE XCOMINQ FILE WILL CONTAIN BOTH REQUEST NUMBERS THE XCOMINQ FILE CAN CONTAIN MULTIPLE REQUESTS HOWEVER ALL REQUESTS MUST BE SCHEDULED VIA THE SAME XCOMPLEX ADMIN STEP 2 EXEC PGM XCOMJOB PARM TYPE SCHEDULE ACBNAME XCPT DFLTAB XCOMDFLT STCAPPL XCPT STEPLIB DD DSN CAT CAILIB DISP SHR LOADLIB DD DISP SHR DSN CEE SCEERUN IBM C RUNTIME SYSTCPD DD DSN TCPIP TCPIP DATA DISP SHR IBM TCP IP XCOMINQ DD DISP SHR DSN XCOM RBO XCOMINQ XCOMCNTL DD DISP SHR DSN XCOM RBO XCOMCNTL SYSPRINT DD SYSOUT TCP IP MSGS SYSTERM DD SYSOUT TCP IP MSGS SYSINO1 DD TYPE SEND sies FILETYPE FILE FILEOPT REPLACE C 28 User Guide Sample XCOMJOB Inquire JCL through the XCOMPLEX Admin Server Member XCOMJOXI 77 7 LP 77 THIS STEP USES XCOMJOB TYPE INQUIRE TO DETERMINE THE STATUS OF THE TRANSFER REQUESTS RECORDED IN THE XCOMINQ FILE XCOMJOB ISSUES MESSAGE XCOMM655 FOR EACH COMPLETED TRANSFER AND REMOVES THE TRANSFER NUMBER FROM THE XCOMINQ FILE IF ANY OF THE TRANSFERS SPECIFIED IN THE XCOMINQ FILE IS ACTIVE OR SUSPENDED XCOMJOB WAITS UNTIL IT COMPLETES OR IF THE TIME INTERVAL SPECIFIED BY INQWAIT ELAPSES BEFORE ALL TRANSF
173. SYSOUT SYSPRINT DD SYSOUT XCOMGLOB DD DSN XCOM RBO GLOBAL DISP SHR FOR TYPE EXECUTE XCOMREST DD DSN XCOM RBO RESTART DISP SHR FOR TYPE EXECUTE SYSUDUMP DD SYSOUT SYSINO1 DD DSN amp TEMP DISP NEW DELETE DELETE SPACE TRK 1 1 DCB LRECL 80 BLKSIZE 8000 RECFM FB UNIT SYSDA The Programming Interface 4 5 Calling Unicenter CA XCOM Data Transport from an Assembler Program Calling Unicenter CA XCOM Data Transport from an Assembler Program Use the LOAD macro to load a new copy of the Unicenter CA XCOM Data Transport routine into main storage Use the DELETE macro to delete the program from main storage Sample Assembler Program The following is a sample fragment of an Assembler program ELIT 2 ech bora sedes This program shows how to invoke XCOMJOB from an assembler program On entry it is assumed that the control statements for the transfer request reside in the data set allocated to the 5 5 01 DD statement XCOMJOB is then loaded into storage and receives control via a BALR instruction On return it is removed from storage via a DELETE SVC ASMSAMP CSECT ASMSAMP AMODE 31 ASMSAMP RMODE 31 ox ox STM R14 R12 12 R13 Store entry registers LR 11 15 Load base register USING ASMSAMP R11 Establish addressability GETMAIN RU LV WRKL Request work area storage LR R2 R13 Keep current save are
174. Servers although this is not a requirement The XCOMPLEX Worker Servers connect to the XCOMPLEX Admin Server automatically if the TYPE ADMIN destination member is defined in the XCOMCNTL data set in the server JCL and included in the START member If the XCOMPLEX Admin Server is not up when the XCOMPLEX Worker Server is brought up the XCOMPLEX Worker Server retries the connection every 2 minutes for up to an hour The connection may also be made manually by enabling the dest member for the XCOMPLEX Admin Server and issuing a CNOS modify command to the XCOMPLEX Admin Server To start a Unicenter CA XCOM Data Transport XCOMPLEX Worker Server enter one of the following commands on the z OS console or any TSO ISPF or NETVIEW session where the user is authorized to invoke z OS system commands START XCOMA S XCOMA Operation and Control 6 3 Using the Unicenter CA XCOM Data Transport MODIFY Commands Several informational messages are displayed when Unicenter CA XCOM Data Transport is started as shown in the following example XCOMM1000I STARTING CROSS SYSTEM COUPLING FACILITY SERVICE TASK XCOMM0330I PRIMARY SUBSYSTEM IS JES2 00561 UNICENTER R CA XCOM R r11 GEN LEVEL 0410 5 00 IS UP AND ACCEPTING LOGONS 00561 ON CPU 2064 SERIAL 240AA1 IN 31 BIT MODE MVS SP7 0 2 0803 STARTING XCOM TCP IP LISTENER XCOMM1019I XCF CONNECT STR XCOMPLEX QA CONN XCPS RC 00000000 5 00000000 DISP OLD XCOMM1020I MAXI
175. Specifies the unit name to be used in locating the local data set Value Definition to 8 alphanumeric Specifies the unit name to be used in locating the local characters data set Notes Used in conjunction with the local VOLUME parameter Default Catalog information is used MVS Extended Tape Parameter Entry The MVS Extended Tape Parameter Entry screen is used to enter information relating to the use of magnetic tape in transfer processing Screen The MVS Extended Tape Parameter Entry screen is displayed when Y is entered in the Tape field on the Send MVS File To Another System screen described in the preceding section or the Receive File From Another System screen described later in this chapter sample MVS Extended Tape Parameter Entry screen follows 04 10 26 Unicenter CA XCOM r11 5 00 TURKIO1 MVS Extended Tape Parameter Entry YES i NO File Sequence nnnn range 1 to 9999 Label Type SLINLINSLISULIBLPILTMIALIAUL Unit Count nn range 1 to 20 Volume Sequence nnn range 1 to 255 Output Tape Parameters Density 1121314 Volume Count nnn range 1 to 255 Expiration Date yyddd yyyy ddd nnnn note nnnn is retention period in days 1 Help COMMANDS gt 1 1 F2 SPLIT F3 End F4 RETURN F5 RFIND 6 F7 UP F8 DOWN F9 SWAP FlO0 Language F11 Hold F12 Alloc 2 38 User Guide Parameter Fields Tape File Sequence Label Type MVS Extend
176. T VARY BASED ON THE OPERATING SYSTEM IN USE OBO OK KOK KOR K K KOR K KOK OR K K ARK SYSMDUMP DD DSN amp PREFIX SYSMDUMP DISP SHR SYSTEM DUMP C 22 User Guide Sample CICS Notification Transaction Member XCOMSAMP Sample CICS Notification Transaction Member XCOMSAMP The following is a copy of the sample CICS Notification Transaction found on the distribution tape CAI CINBOSAM XCOMSAMD This illustrates a CICS COBOL program LERRA PE Die suu IR E NL pq c ID DIVISION XCOMSAMP AUTHOR COMPUTER ASSOCIATES INTERNATIONAL ENVIRONMENT DIVISION DATA DIVISION WORKING STORAGE SECTION 77 IN MSG PIC X 2000 VALUESPACES 77 OUT MSG 40 VALUESPACES 77 MSG LENGTH PIC 59 4 COMP SYNC PROCEDURE DIVISION MAINLINE LOGIC THE BACK END TRANSACTION STARTS IN STATE 5 RECEIVE STATE IT MUST ALWAYS DO A RECEIVE NOTE THAT YOU DO NOT NEED TO CODE EXEC CICS ALLOCATE NOR EXEC CICS CONNECT PROCESS SINCE THIS IS THE TARGET SIDE OF THE CONVERSATION IT IS NOT NECESSARY TO SPECIFY THE CONVERSATION ID ON THE EXEC CICS RECEIVE COMMAND SINCE THE LU 6 2 ISC SESSION IS THE PRINCIPLE FACILITY OF THIS TRANSACTION WHEN THE CA XCOM STARTED TASK ALLOCATES A CONVERSATION TO THIS PROGRAM IT WILL SEND A HISTORY RECORD RIGHT AWAY THAT WILL DESCRIBE THE FILE TRANSF
177. TA CISZ 4096 INDEX NAME XCOM X XCOMRECP AIX INDEX CISZ 1024 AIX XCOM X XCOMUSER AIX RELATE XCOM X XCOMHIST SHR 2 3 NONUNIQUEKEY UPGRADE RECSZ 20 300 VOL VVVVVV CYLINDERS 1 1 KEYS 20 28 DATA NAME XCOM X XCOMUSER AIX DATA CISZ 4096 INDEX XCOM X XCOMUSER AIX INDEX CISZ 1024 AIX XCOM X XCOMIDNT AIX RELATE XCOM X XCOMHIST SHR 2 3 NONUNIQUEKEY UPGRADE RECSZ 20 300 VOL VVVVVV CYLINDERS 1 1 KEYS 18 98 DATA NAME XCOM X XCOMIDNT AIX DATA CISZ 4096 INDEX NAME XCOM X XCOMIDNT AIX INDEX CISZ 1024 IDS XCOM X XCOMHIST 005 0 0 AIX IDS XCOM X XCOMHIST ODS XCOM X XCOMRECP AIX IDS XCOM X XCOMHIST ODS XCOM X XCOMUSER AIX BIX DEF DEF DEF DEF Sample History File Creation JCL Member DEFHIST IDS XCOM X XCOMHIST ODS XCOM X XCOMIDNT AIX PATH PENT PATH PENT PATH PENT PATH PENT NAME XCOM XCOM X XCO NAME XCOM XCOM X XCO NAME XCOM XCOM X XCO NAME XCOM XCOM X XCO X XCOMREQ PATH MREQ AIX UPDATE X XCOMRECP PATH RECP AIX UPDATE X XCOMUSER PATH USER AIX UPDATE X XCOMIDNT PATH MIDNT AIX UPDATE Sample Files 5 Sample XCOMUTIL Job Member XCOMUTIL Sample XCOMUTIL Job Member XCOMUTIL The following is a copy of the sample XCOMUTIL Job found on the distrib
178. TER VALUE1 VALUE2 VALUEG HOLDCOUNT XTCERRDECR XTCERRREL SYSINO1 Parameters Associates a number with a transfer request that is incremented or decremented by the successful or unsuccessful completion of other transfer requests As long as the number is greater than 0 the transfer is not released Value Definition 0 to 255 Specifies a value that controls the holding releasing of a transfer request The transfer is released when the value of the parameter reaches 0 Notes See the description of the parameters XTCERRDECR XTCERRINCR XICGOODDECR and XTCGOODINCR which can decrement and increment the value of the HOLDCOUNT parameter Default 0 Specifies the transfer requests for which the HOLDCOUNT parameter value is decremented when the current transfer completes unsuccessfully Value Definition Up to 8 transfer Specifies up to eight transfers whose hold counts are to be request names decremented if a transfer completes unsuccessfully Notes VTAM errors are not considered failed file transfers since they are retried later Specifies the transfers to be released if the current transfer completes unsuccessfully Value Definition Up to 8 transfer Specifies up to eight transfers to be released if the current request names transfer completes unsuccessfully The Batch Interface 3 75 SYSINO1 Parameters XTCERRINCR Specifies the transfer requests for which the HOLDCOUNT parameter value is incremented if the cur
179. TRACE None The trace function dynamically allocates a SYSOUT file to receive the trace data This SYSOUT file s class is defined through the DUMPCL parameter of Unicenter CA XCOM Data Transport s Default Options Table see the Unicenter CA XCOM Data Transport for z OS Administrator Guide It can be overridden in the EXEC PARM of the Unicenter CA XCOM Data Transport started task Turning on the XTRACE seriously degrades performance To turn off the trace use the NOXTRACE command Using the Unicenter CA XCOM Data Transport MODIFY Commands Command Security Requirements The use of the command requires that the security authorization for the command issuer contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec XTRACE The applsec variable represents the value of the APPLSEC parameter in the Default Options Table Operation and Control 6 53 Processing Different File Types This chapter covers Unicenter CA XCOM Data Transport support for various file types including partitioned data sets PDS partitioned data set extended PDSE and PDSE program libraries generation data groups VSAM files and magnetic tape resident files Processing requirements limitations and special features for different file types are described in detail Unless explicitly stated otherwise these considerations apply uniformly across all the Unicenter CA XCOM Data Tra
180. Transport Default Options Table This value is specified in seconds Scanning cannot be turned off Report transfers are single threaded Only one report is sent to each destination per scan of the spool The MAXRPTB parameter in the default table specifies the maximum block size in bytes that Unicenter CA XCOM Data Transport uses to write reports on the spool Temporary report data sets are written according to the PSOVOL and PSOUNIT specified in the default table and start with a high level qualifier specified by PSOPREF in the default table If PSOSECUR YES EXIT05 is called The PSODISP parameter in the default table specifies what happens to the temporary report data set on the JES Spool if the report cannot be delivered If PSODISP KEEP these temporary data sets are retained if there is a problem If PSODISP DELETE these temporary data sets are deleted if there is a problem and the report must be requeued to try again The PSOCKPT parameter in the default table allows you to specify different checkpoint values for the report transfer The default value is 1000 Turn off checkpointing by specifying PSOCKPT 0 You may override the value by specifying PSOCKPT in the dest member as DEST STEPOO1 EXEC PGM IEBGENER SYSPRINT DD SYSOUT SYSUT1 DSN XCOM TEST TRANSFER DISP SHR SYSUT2 DD SYSOUT 1 DEST XCOMABC SYSIN DD DUMMY Sample DEST Member DEST TYPE DEST DEST XCOMABC IPNAME 141 202 156 2 Sample JCL to
181. U defined for parallel sessions For those LUs use the CNOS command described later in this chapter The ACTIVATE command is not used for TCP IP destinations Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Resource Name Level UPDATE XCOM applsec ACTIV ATE destname The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the LU to be activated Note Do not specify a group name because Unicenter CA XCOM Data Transport interprets this as an individual LU name Operation and Control 6 7 Using the Unicenter CA XCOM Data Transport MODIFY Commands ALTER Command Format Operands 6 8 User Guide Alters date time scheduling priorities or execution priorities F XCOM ALTER nnnnnn TIME SPRTY nn EPRTY nnn The following operands are used with the ALTER command Operand Description DATE Alters the starting date of the file transfer with request number nnnnnn The new starting date may be coded in one of two formats m yyyymmdd where yyyy is a 4 digit designation for a year for example 2005 mm is a 2 digit designation for one of the twelve months of the year as shown in the following
182. Unicenter CA ACOM Data Transport forz 0 User Guide rii Computer Associatese J02572 2E This documentation and related computer software program hereinafter referred to as the Documentation is for the end user s informational purposes only and is subject to change or withdrawal by Computer Associates International Inc CA at any time This documentation may not be copied transferred reproduced disclosed or duplicated in whole or in part without the prior written consent of CA This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties Notwithstanding the foregoing licensed users may print a reasonable number of copies of this documentation for their own internal use provided that all CA copyright notices and legends are affixed to each reproduced copy Only authorized employees consultants or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies This right to print copies is limited to the period during which the license for the product remains in full force and effect Should the license terminate for any reason it shall be the user s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed To the extent permitted by applicable law CA provides this documentation as is without warranty of any kind inclu
183. Unicenter CA XCOM Data Transport transfers the designated file when the request is made This is done regardless of whether a generation data set is specified by its relative generation number or its 00 suffix If the local file is specified as LFILE it is transferred according to its relative generation number This permits maximum flexibility without alteration of the production JCL Menu Interface Generation Data Groups If the LCLDS01 DD is used to create a 1 GDG version for TYPE SCHEDULE transfer there are additional potential problems a When the z OS JCL performs the allocation of the LCLDS01 DD it allocates and potentially catalogs the new version depending on the value of the DISP parameter in the JCL This new version does not have an end of file mark because it has not yet been opened and closed by a program When the transfer begins on the Unicenter CA XCOM Data Transport started task it allocates a new 1 version of the GDG In cases where the transfer is successful this results in the creation of two new generations of the GDG The first version contains garbage because it was allocated by the z OS JCL processor and was never opened or closed by a program to write an end of file mark If the transfer fails under certain conditions the version allocated by the Unicenter CA XCOM Data Transport started task may be deleted This leaves the version of the allocated by the z OS JCL processor as the curr
184. Unicenter CA XCOM Data Transport is stopped in this way normal cleanup of transfer requests do not occur Using the Unicenter CA XCOM Data Transport MODIFY Commands Notes When stopping Unicenter CA XCOM Data Transport does not allow new locally initiated and remotely allocated transmissions to commence Other ways to stop Unicenter CA XCOM Data Transport include the following non MODIFY commands Command Description C XCOM DUMP Whether issued in the form C XCOM or C XCOM DUMP this command causes Unicenter CA XCOM Data Transport to stop immediately and unconditionally without any cleanup of transfer requests that is it has the same effect as the MODIFY command F XCOM STOP IMMED PXCOM When this command is issued once it has the same effect as the MODIFY command F XCOM STOP that is Unicenter CA XCOM Data Transport does not stop until all transfers in progress at the time of issuing the command have completed When the command is issued a second time for a job it has the same effect as the MODIFY command F XCOM STOP IMMED or the non MODIFY command C XCOM DUMP Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name CONTROL XCOM applsec STOP type The variable represents the following value m applsec the value of the APPLSEC parameter in the D
185. Xed CASe Explanation A literal Enter exactly as shown In the preceding example enter F XCOM exactly as shown A variable Replace with an appropriate value Enter in one of two ways Inlong form by spelling out the item in uppercase for example the long form of ACTivate is ACTIVATE m In short form by using only the capitalized letters for example the short form of ACTivate is ACT A numeric variable For example represents any number in the range 0 to 9 and nn is any number in the range 00 to 99 Items separated by Items in braces Items in brackets Indicates that the items are alternatives one of the items must be chosen Indicates required items One of the items in braces must be chosen Indicates optional items In such cases you may specify one more or none of the items enclosed in the brackets Using the Unicenter CA XCOM Data Transport MODIFY Commands ACTIVATE Command Format Operands Notes Starts a single session with the specified LU If the LU is not available the request is queued If a session has already been established with the LU an error message is displayed If this format is entered without an LU name an error message is displayed saying that the LU name is required for this command F XCOM ACTivate destname Operand Description destname Specifies the name of the logical unit to be activated The ACTIVATE command does not work for an L
186. YSINOI parameters 3 28 AGE 3 30 CKPT 3 31 CODE 3 32 COMPRESS 3 33 DATACLAS 3 34 DCB parameters BLKSIZE 3 72 LRECL 3 73 3 73 DOMAIN 3 34 DSNTYPE 3 35 EPRTY 3 36 FILETYPE 3 36 FILETYPE FILE parameters FILEOPT 3 56 3 57 LUNIT 3 58 LVOL 3 58 PACK 3 59 RECSEP 3 60 SPACE 3 60 FILETYPE REPORT parameters CHARS 3 62 CLASS 3 62 CONTROL 3 63 COPY 3 63 DEST 3 64 DISP 3 64 FCB 3 65 FORM 3 65 REPORT 3 65 REPORTHOLD 3 66 SPOOL 3 66 WRITER 3 66 GROUP 3 37 HOLD 3 38 ID 3 38 INOWAIT 3 39 IPNAME 3 39 IPPORT 3 40 JPNCNTL 3 40 JPNDATA 3 41 JPNDBL 3 41 JPNSHFT 3 41 LFILE 3 42 LIST 3 42 LPASS 3 43 LU 3 43 LUSER 3 44 MGMTCLAS 3 45 NEWXFER 3 45 NOTIFY 3 46 NOTIFYNAME 3 47 PASSWORD 3 47 PROGLIB 3 48 RESTART 3 49 RNOTIFY 3 49 RNOTIFYNAME 3 50 SECURE SOCKET 3 50 SPRTY 3 51 STARTDATE 3 51 STARTTIME 3 52 STORCLAS 3 52 SYSUDATA 2 29 2 60 2 75 2 92 3 53 tape parameters DEN 3 67 EXPDT 3 67 LABEL 3 68 LLABEL 3 69 LUNITC 3 70 LVOLCT 3 70 LVOLSO 3 70 REIPD 3 70 3 71 UNITCT 3 71 VOLCT 3 71 VOLSO 3 71 TDUDATA 3 53 transfer control XTC parameters HOLDCOUNT 3 75 XTCERRDECR 3 75 XTCERRINCR 3 76 XTCERRPURGE 3 76 XTCERRREL 3 75 XTCGOODDECR 3 76 XTCGOODINCR 3 77 XTCGOODPURGE 3 77 XTCGOODREL 3 77 XTCJOB 3 77 XTCNET 3 78 TRUNCATE 3 53 TYPE 3 54 USER 3 54 USERID 3 54 VOL 3 61 SSL 3 55
187. YSUT1 DD UNIT SYSALLDA SPACE 1700 6000 100 SYSUT2 DD UNIT SYSALLDA SPACE 1700 6000 100 SYSUT3 DD UNIT SYSALLDA SPACE 1700 6000 100 SYSPRINT DD SYSOUT SYSIN DD DSN XCOM RVRMP CINBOSAM XCOMTOPS DISP SHR SYSPUNCH DD DUMMY SYSOUT B SYSLIN DD DSN amp amp OBJSET DISP NEW PASS UNIT SYSALLDA SPACE 80 2000 500 LKEDTOPS EXEC PGM IEWL COND 4 LT ASMTOPS PARM XREF LET LIST NCAL AC 1 NORENT NOREUS NOTEST NOREFR SYSPRINT DD SYSOUT SYSUT1 DD UNIT SYSALLDA SPACE 1024 500 20 SYSLMOD DD DSN XCOM RVRMP LOAD DISP SHR SYSLIN DD DSN amp amp OBJSET DISP OLD DELETE DD ENTRY XCOMTOPS NAME XCOMTOPS R ASMTOP2 EXEC 5 90 PARM SYSPARM UID OBJECT NODECK XREF SHORT NORENT SYSLIB DD DSN XCOM RVRMP MACLIB DISP SHR DD DSN SYS1 MACLIB DISP SHR DD DSN SYS1 AMODGEN DISP SHR DD DSN SYS1 MODGEN DISP SHR SYSUT1 DD UNIT SYSALLDA SPACE 1700 6000 100 SYSUT2 DD UNIT SYSALLDA SPACE 1700 6000 100 SYSUT3 DD UNIT SYSALLDA SPACE 1700 6000 100 Sample Files 31 Sample JCL for Reassembling and Link Editing XCOMTOPS Member ASMTOPSU C 32 User Guide SYSPRINT DD SYSIN DD SYSPUNCH DD SYSLIN DD T5 SYSOUT DSN XCOM RVRMP CINBOSAM XCOMTOP2 DISP SHR DUMMY SYSOUT B DSN 8 amp amp 0BJSET DISP NEW PASS UNIT SYSALLDA SPACE 80 200
188. ZWLM WORKUNIT SIZE 3840 PREFLIST CFCCXCOM STRUCTURE NAME SYSIGGCAS ECS SIZE 3840 PREFLIST CFCCXCOM Sample Files 19 Sample XCOMPLEX Admin Server Sample XCOMPLEX Admin Server The following is a copy of the sample Unicenter CA XCOM Data Transport JCL found on the distribution tape CALCINBOSAM XCOMADM This JCL illustrates the definition of the Unicenter CA XCOM Data Transport XCOMPLEX Admin Server XCOMADM PROC PREFIX XCOM RBO HIGH LEVEL DATA SET NAME QUAL CA XCOM FOR MVS ADMIN SERVER ADDRESS SPACE RRR KK KK KK KK KK KKK KK KK KK SERVER EXEC PGM XCOMXADM TIME 1440 REGION 5120K PARM ACBNAME XCOMAPPL OVERRIDE DFLT STEPLIB DD DSN amp PREFIX CAILIB DISP SHR LOAD MODULES XCOMCNTL DD DSN amp PREFIX XCOMCNTL DISP SHR CONTROL LIBR XCOMRRDS DD DSN amp PREFIX RRDS DISP SHR ACTIVE REQSTS XCOMHIST DD DSN amp PREFIX DISP SHR DONE REQUESTS XCOMREQ DD DSN amp PREFIX XCOMREQ PATH DISP SHR ACCESS PATH XCOMUSER DD DSN amp PREFIX XCOMUSER PATH DISP SHR ACCESS PATH XCOMIDNT DD DSN amp PREFIX XCOMIDNT PATH DISP SHR ACCESS PATH XCOMRECP DD DSN amp PREFIX XCOMRECP PATH DISP SHR ACCESS PATH SYSPRINT DD SYSOUT TCP IP MSGS
189. a address LR R13 R1 Load work area address USING WRK R13 Establish addressability LR R14 R1 Load registers for MVCL LA R15 WRKL SLR RO RO LR 1 0 MVCL R14 R0 Clear work area to zeros ST R2 WRKSAVE 4 Chain save areas ST R13 8 R2 LOAD EPLOC XCOMJOB Load XCOMJOB into storage LA R1 PARMADDR Point to parm list address LR R15 R0 Load entry point address BALR R14 R15 Invoke XCOMJOB DELETE EPLOC XCOMJOB Remove XCOMJOB from storage LR R1 R13 Load work area address L R13 WRKSAVE 4 Unchain save areas FREEMAIN RU LV WRKL A 1 Free work area storage LM R14 R12 12 13 Continued Continued BR R14 4 6 User Guide 8 Calling Unicenter CA XCOM Data Transport from an Assembler Program PARMLIST DS 0D XCOMJOB parameter list PARMLEN DC AL2 L PARMDATA Parameter list length PARMDATA DC C TYPE EXECUTE ACBNAME XCOMAPPL LU DENVER X Parameters XCOMJOB DC CL8 XCOMJOB XCOMJOB program name WRK DSECT Local work area WRKSAVE DS 18F Register work area length REGS END ASMSAMP The Programming Interface 4 7 The Remote Spooling Feature Process SYSOUT This chapter describes how Unicenter CA XCOM Data Transport executes file transfers from a local z OS system to other systems through the JES2 or JES3 spool Basics of JES Spool Use This section describes the basics of how Unicenter CA XCOM Data Transport uses the JES2 or JES3 spool to execute file transfers from a local z OS
190. a sets nnnn Specifies the new value 0 9999 of the Unicenter CA XCOM Data Transport parameter identified in the DFLT command Operation and Control 6 17 Using the Unicenter CA XCOM Data Transport MODIFY Commands Notes The values of these parameters are defined in the Default Options Table Use the INQ command to display the current values Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Resource Name Level UPDATE XCOM applsec DFLT parmname The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m parmname the name of the parameter to which the DFLT is applied that is any or all of the operands listed above DISABLE Command Disables a Unicenter CA XCOM Data Transport control library member Format F XCOM DISAble membername Operands The following operand is used with the DISABLE command Operand Description membername Specifies the name of the control library member containing the definition of the LU or a group of LUs to be disabled The member name can contain up to 8 alphanumeric characters 6 18 User Guide Using the Unicenter CA XCOM Data Transport MODIFY Commands Notes This command disables a group s control library member allowing the user to change parameters in Un
191. allocating a new SMS managed data set Note This parameter applies only to mainframe SMS data sets Default None Send Report To Another System Screen Dataset Name Type Specifies the data set definition Note This parameter applies only to mainframe SMS data sets Value Description LIBRARY Defines a PDSE PDS Defines a partitioned data set blank Defines a partitioned or sequential data set based on the data set characteristics entered Note These values IBM standards for SMS processing Range 1 to 8 characters Default None Send Report To Another System Screen The Send Report To Another System screen is used to submit a z OS data set for printing on a remote system The data set being sent must exist as a valid cataloged data set on the sending system The file is sent with embedded control characters for example ASA Machine retained 04 10 26 Unicenter CA XCOM r11 5 00 Send Report To Another System TURKIO1 Transfer ID Local File Name Local Tape Info File Seq Secure Socket SSL NO Execution Priority Label Type Unit Count Vol IP Name Addr 122 222 222 222 Print Destination Report Title Form Record Separators EBCDIC Binary ASCII Truncate Record Code Table Remote System Information User ID Password Domain Notify User PFK 1 Help COMMAND gt F1 Help F2 SPLIT F7 UP F8 DOWN 3 End F3 End F9 SWAP F1l0 Language 11
192. ally exclusive parameters One of these parameters must be coded either on the EXEC card or in SYSINO1 Coding more than one causes an error Specifies a user ID on the source computer whose access privileges are used to execute the file transfer Value Definition XXXXXXXX Specifies up to eight alphanumeric characters representing a user ID whose access privileges on the source computer are used for the file transfer Notes LUSER is mainly used for a third party transfer a user on system A requests that system B source execute a file transfer to system C target While the transfer request is initiated by system A the file transmission is entirely between system B and system C The only prerequisites for third party transfers are m All systems must be identified to VTAM and be running Unicenter CA XCOM Data Transport Version 2 or higher m The ID entered for LUSER must satisfy the requirements of the security software in effect on the source system If the source computer has a default user ID for third party file transfers and you want to use this default then a null value must be specified for this parameter as LUSER with at least one space between the quotes Not all Unicenter CA XCOM Data Transport platforms support third party transfers MGMTCLAS NEWXFER SYSINO1 Parameters For conventional file transfer LUSER can be used to identify the user initiating the transfer This is useful in performing operato
193. ame Part device Description A disk drive name If the device is not specified the default provided in the SYSUAF as defined on the DEC system for that user is used Range 1 to 15 characters Note The Unicenter CA XCOM Data Transport remote USERID field determines the SYSUAF USERID directory filename type version Directory and subdirectory information If this information is not provided defaults will be selected as described under device above Note Unicenter CA XCOM Data Transport accepts angle brackets lt gt in OpenVMS file names which are converted to square brackets on the DEC computer Example PLAYERS1 lt BRIDGE gt CARD DAT is treated as equivalent to PLAYERS1 BRIDGE CARD DAT The specific file within the directory OpenVMS null file names are used if the file name and type are not provided The version of the file The OpenVMS operating system can keep multiple versions of a file each time that file is saved It is normal to omit this number to indicate that you want the most recent version of a file the highest version number For further information on OpenVMS file specifications see the OpenVMS documentation Restrictions OpenVMS The following restrictions apply to Unicenter CA XCOM Data Transport for OpenVMS Alpha and Unicenter CA XCOM Data Transport for OpenVMS V AX Specifying transfer type All transfers must be TYPE SCHEDULE for batch or QUEUED from ISPF
194. ana characters Default E Delete Shift Specifies whether DBCS shift out and shift in characters are removed or converted to spaces Value Definition C The DBCS shift out and shift in characters are converted to spaces D The DBCS shift out and shift in characters are removed Default D Double Byte Code Identifies the local double byte character set for Japanese conversions Note This parameter is no longer supported IBM double byte character set only is supported 2 100 User Guide File Transfer Scheduling Information Screen File Transfer Scheduling Information Screen The File Transfer Scheduling Information screen contains the optional parameters related to file transfer scheduling This screen is displayed only if a file transfer is requested to be queued via the Queue for Execution field on the Primary Option Menu and the user enters the SCHEDULE command PF11 23 from any of the file transfer screens Send MVS File To Another System Submit Job To Another System Send Report To Another System or Receive File From Another System 04 10 26 Unicenter CA XCOM r11 5 00 LOGDAO1 File Transfer Scheduling Information LOGDAO1 R30 CICS ASM XCICODIS Start Date Day 17 Month 09 Year 2002 or Number of days from today Start Time 0949 HHMM HHMM or Selection Priority 1 255 Hold Y or N 1 999 1 Help 3 End 12 Alloc COMMAND gt 1 1 F2 SPLIT F3 End F4 RETURN F
195. anch entry Required DSECT EX13PLST is the required DSECT Addressing Mode at Entry The addressing mode at entry is 31 User Exits D 25 User Exit 13 Registers at Entry Registers at Exit Valid Return Code Sample Program D 26 User Guide The following registers are available at entry Register Description RO Undefined R1 Address of EX13PLST R2 to R12 Undefined R13 Address of register save area R14 Return address R15 Entry point address The following registers are available at exit Register Description RO to R14 Undefined R15 Return code The only valid return code is 0 for a normal return Return Code Description 0 Allow access immediately 4 Let the security package make the decision 8 Deny access immediately The following is a sample program using this exit CAI CINBOSAM XCOMEX13 Note Exit 13 has six separate entry codes mapped by the field XI3FUNCT in the EX13PLST DSECT This field contains an entry code explaining why the exit is being entered Index A ACBNAME PARM parameter 3 9 ACTIVATE MODIFY command 6 7 active session display with command line 6 20 ACTIVE status field 2 118 add remote file 2 23 2 86 Advantage CA Roscoe transactions 5 2 AGE SYSINOI parameter 3 30 system parameter 6 16 XCOMUTIL parameter B 3 allocating data sets local 4 2 new 2 3 2 43 6 16 6 17 temporary 6 17 ALTER MODIFY command 6 8 APPC DECnet 5 application program
196. and the Universal Naming Convention UNC The file naming conventions for Windows NT are similar to those for Windows with some significant differences some of which are outlined below Use the following format to name files when using standard Windows NT file names d directory nameN N f lename ext Use the following format to name files when using UNC file names server name share name directory filename The following table describes the parts of Windows NT file names and UNC file names Part Description d Required A particular device indicated as a drive letter directoryname Required One or more optional directories and subdirectories Subdirectories can take the form of name ext Note The form of the directory name and file name depend on the operating system running on the server Windows NT 2000 and XP Part Description filename Required The name of the data file For FAT file systems filename is 1 to 8 characters NTFS and HPFS file systems support long file names up to 256 characters including the extension Names may or may not be case sensitive depending on the file system on the server For FAT NTFS and HPFS names are not case sensitive You can use uppercase and lowercase when creating a name and they will display as typed but internally Windows NT makes no distinction for this For example Windows NT would consider MYFILE and MyFiLe as references to the same file Windows
197. ank parameter value to the source system enter inserting at least one blank space between the quotation marks Do this when the source system supplies its own default value for the user ID under whose access privileges the file transfer is to execute on the source system Default TSO user ID The Menu Interface TSO ISPF Panels 2 63 Send Report To Another System Screen Password Domain Notify User 2 64 User Guide Identifies the password associated with the above user ID This value is not displayed Value Definition Up to 31 Specifies up to 31 alphanumeric characters representing the alphanumeric password associated with the above user ID characters Identifies the Windows 2000 2003 or XP domain associated with the remote server Value Definition Up to 15 Specifies up to 15 alphanumeric characters representing the alphanumeric domain user password and ID associated with the remote characters server Notes Can be used for transfers running under Windows 2000 2003 or XP only Identifies the user on the local system Unicenter CA XCOM Data Transport is to notify once the transfer completes Value Definition Up to eight Specifies the user ID whose privileges are used for executing alphanumeric this file transfer on the local computer characters Default LOG Submit Job To Another System Screen Submit Job To Another System Screen The Submit Job To Another System screen provides Unicenter CA XCOM
198. ansfer involves a PDS member specify CREATE only if the PDS itself is being created otherwise an error results This is ignored for TYPE EXECUTE transfers that specify TYPE RECEIVE in SYSINO I if the local file is identified through the LCLDS01 DD statement since in this case the disposition of the file is determined by the DISP parameter on the DD statement Default REPLACE The Batch Interface 3 57 SYSINO1 Parameters LUNIT LVOL Specifies the unit for the local file involved in this file transfer If LCLDS01 is used the unit can be specified through the JCL parameter UNIT Value Definition Up to 8 Specifies the unit for the local file involved in this unit transfer characters Notes LUNIT is used with the LFILE parameter Default Catalog information or default specified in Unicenter CA XCOM Data Transport Default Options Table Specifies the volume of the local file involved in a file transfer This is used with the LFILE parameter Value Definition Up to 6 Specifies the volume of the local file involved in a file transfer characters Notes If LCLDSOI is used the volume can be specified through the VOL parameter Default Catalog information 3 58 User Guide PACK SYSINO1 Parameters Indicates whether record packing is used Record packing is available in Unicenter CA XCOM Data Transport for z OS for version 2 type transfers It can substantially improve performance Value Definition CRL
199. ansport writes the SYSINO1 parameters for the file transfer in addition to performing the file transfer Value Definition XXXX XXX XXXXXXXX Specifies the name of a data set where Unicenter CA XCOM Data Transport writes the SYSINO1 parameters used for a transfer Notes Specifying this field allows a user to save the SYSINO1 parameters for an ISPF initiated file transfer so that the user can execute a batch job to perform the same file transfer at a later date The PASSWORD parameter will be saved as encrypted when an unencrypted SYSINO1 is saved The Unicenter CA XCOM Data Transport Batch accepts the PASSWORD in encrypted and non encrypted format The data set named in this field must be an existing physical sequential file or a member of a PDS If this field does not contain a value Unicenter CA XCOM Data Transport does not save the SYSINO1 parameters The Menu Interface TSO ISPF Panels 2 13 The Primary Option Menu Only Save SYSINO1 2 14 User Guide Specifies whether or not Unicenter CA XCOM Data Transport should only save the SYSINO1 parameters or both save the parameters and initiate the transfer Value Definition Y Unicenter CA XCOM Data Transport only writes the SYSINO1 parameters to the data set specified in the Save SYSINO1 in DS name field Unicenter CA XCOM Data Transport does not initiate a file transfer N Unicenter CA XCOM Data Transport saves the SYSINO1 parameters and initiates the file transfer No
200. applied to this data set is BLP Specifies the number of units to be allocated on the local system Value Definition 1 to 20 Specifies the number of units to be allocated on the local system The Batch Interface 3 69 SYSINO1 Parameters LVOLCT LVOLSQ RETPD 3 70 User Guide Specifies the maximum number of volumes to be used in processing a multivolume output tape data set on the local system Value Definition 1 to 255 Specifies the maximum number of volumes to be used in processing a multivolume output tape data set on the local or remote system Specifies the sequence number of the first volume of a multi volume remote data set to be used Value Definition 1 to 255 Specifies the sequence number of the first volume of a multivolume remote data set to be used Specifies the number of days to retain the tape data set being created Value Definition 11099992 Specifies the number of days 1 to 9999 that the tape data set being created is to be retained Default None Notes RETPD and EXPDT are mutually exclusive specify one or the other TAPE UNITCT VOLCT VOLSQ SYSINO1 Parameters Indicates to the remote system whether the volume is a tape volume or a disk file Value Definition YES Indicates that the transfer is to a tape volume and that mounts are allowed when performing dynamic allocation NO Indicates that the transfer is to a disk file Specifies the number of units to be all
201. aracters identifying the code table to be used by the remote partner Specifies the name of an external writer that is to process the report on the remote system Value Definition Up to eight Specifies the name of an external writer that is to process the alphanumeric report on the remote system characters Notes This parameter may be specified for Version 2 type transfers Print Class Hold Printing Forms Control Buffer Send Report To Another System Screen Specifies the print class for this report on the remote system This value is dependent on the remote system Value Definition x Specifies one alphanumeric character representing the print class for this report on the remote system This value is dependent on the remote system Notes When sending a report to a Digital Equipment Corp VAX computer a valid value must be specified for Print Class or the print job fail Default A Indicates whether the report should be held when it is received on the remote system or readied for immediate printing Value Definition Y The report is held N The report is printed immediately Default N Specifies the FCB name used JES from SYS1 IMAGELIB when the report is sent to a remote z OS system Value Definition Xxxx Specifies up to four alphanumeric characters representing the FCB name used by JES from SYSI IMAGELIB when the report is sent to a remote z OS system The Menu Interface TSO ISPF Panels 2 57
202. arameters See also PARM parameters and SYSINO1 parameters application programming interface 4 1 defaults 2 2 Detailed File Transfer screen 2 122 errors 2 122 File Allocation Information screen 2 43 File Transfer Scheduling Information screen 2 103 hierarchy of usage 3 8 history log 2 110 operator control 2 5 PARM 3 3 Index 8 User Guide primary processing 2 4 2 6 Receive File From Another System screen local system 2 96 Receive File screen 2 81 Send File screen 2 16 local system 2 34 Send Report screen 2 48 local system 2 63 remote system 2 61 Submit Job screen 2 66 local system 2 78 remote system 2 75 Transfer Request Display screen 2 110 2 117 XCOMUTIL B 3 PARM 3 3 EXEC 4 1 PARM parameters 3 9 ACBNAME 3 9 CODETABL 3 30 COMPNEG 3 10 CONTINUE 3 11 DFLTAB 3 11 DISPALG 3 12 DOMAIN 3 12 DUMPCL 3 13 EDESC 3 13 EROUT 3 14 GROUP 3 15 IDESC 3 16 IPNAME 3 17 IPPORT 3 17 IROUT 3 18 LIST 3 19 LOG 3 19 LOGCLASS 3 20 LOGDEST 3 20 LOGMODE 3 21 LU 3 21 NETNAME 3 21 SECURE SCHEDULE 3 22 SICAPPL 3 23 STCIP 3 23 STCPORT 3 23 SWAIT 3 24 TCPSTACK 3 24 TIMEOUT 3 16 3 25 TRACE 3 26 TYPE 3 26 VTAMGNAM 3 27 XCOMPLEX 3 28 partitioned data sets 7 1 partner security overview 8 1 parts of a network A 1 password Receive File From Another System screen local 2 97 Send File screen local 2 35 Send Report screen remote 2 62 2 64 Submit
203. art on the originally scheduled day Specifies a number in the range 1 to 255 to indicate either the execution or scheduling priority of the given file transfer Following the keyword EPRTY this number indicates the new execution priority of the file transfer with request number nnnnnn The lowest execution priority is 1 Following the keyword SPRTY this number indicates the new scheduling priority of the file transfer with request number nnnnnn The lowest scheduling priority is 1 Specifies the transfer request number Alters the scheduling priority of the file transfer with request number nnnnnn The new scheduling priority may be coded in the operand nnn following the keyword SPRTY If the operand nnn is not coded the default value of SPRTY is assumed as the new scheduling priority If several transfers are scheduled to occur at the same time they are initiated in order of their priority numbers Default 16 Alters the starting time hhmm of the file transfer with request number nnnnnn The new starting time may be coded in the operand hhmm following the keyword TIME If the operand hhmm is not coded the default value of TIME is assumed as the new starting time on the originally scheduled date Default 0000 that is midnight Operation and Control 6 9 Using the Unicenter CA XCOM Data Transport MODIFY Commands Notes Operand Description yyddd Specifies a date according to the Julian calendar For instance
204. ata Transport log is sent Value Definition xxxxxxxx Specifies the name of the SYSOUT destination to which the Unicenter CA XCOM Data Transport log is sent The name can be eight alphanumeric characters long Notes For more information on LOGDEST see the description of this parameter in the Unicenter CA XCOM Data Transport Default Options Table in the Unicenter CA XCOM Data Transport for z OS Administrator Guide Overrides the mode name set in the Unicenter CA XCOM Data Transport Default Options Table if the DLOGMOD parameter is set to the value of XCOM Value Definition xxxxxxxx Specifies up to eight alphanumeric characters representing the mode name LU NETNAME PARM Parameters Notes If DLOGMOD VTAM this parameter is ignored For more information on LOGMODE see the description of this parameter in the Unicenter CA XCOM Data Transport Default Options Table in the Unicenter CA XCOM Transport for 2 05 Administrator Guide Defines the remote system s LU name and associated VTAM logical unit name LU Value Definition xxxxxxxx Specifies up to eight alphanumeric characters indicating the remote and associated VTAM LU name Notes GROUP LIST LU and IPNAME are mutually exclusive parameters One of these parameters must be coded either on the EXEC card or in SYSINOT Coding more than one causes an error Specifies the name passed by Unicenter CA XCOM Data Transport to remote systems in CINIT or BIND
205. ata Transport MODIFY Commands DELETE Command Deletes a transfer request from the pending queue Format F XCOM DELete nnnnnn Operands The following operand is used with the DELETE command Operand Description nnnnnn Specifies the request number up to six digits of the transfer request to be deleted Notes Entering this command has no effect if the transfer is active Command Security Requirements The use of the command requires that the security authorization for the command issuer contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec DELETE destname ownername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination involved in the transfer m ownername the user ID under whose security authorization the transfer is performed Operation and Control 6 15 Using the Unicenter CA XCOM Data Transport MODIFY Commands DFLT Command Dynamically modifies certain default table parameters The parameters that may be modified are listed under the Operands section These settings are in place until Unicenter CA XCOM Data Transport is stopped and restarted Format Use the following format with the DFLT command F XCOM DFLT operand nnnn Operands The following operands are used with the DFLT command Operand Description AGE Identif
206. ata Transport partner destination name must match that which is shown by the DISPLAY command Operation and Control 6 21 Using the Unicenter CA XCOM Data Transport MODIFY Commands Notes The dump output is sent to one of two places m The DUMPCL SYSOUT class defined in the Unicenter CA XCOM Data Transport Default Options Table m Anoverride value indicated in the EXEC PARM parameter of the Unicenter CA XCOM Data Transport started task Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec DUMP destname The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination about which the dump data is requested DUMPXCF Command Format Operands 6 22 User Guide For XCOMPLEX Worker Server and XCOMPLEX Admin Server only Takes an SVC dump of the Unicenter CA XCOM Data Transport coupling facility area and dumps the entire XCOMPLEX structure F XCOM DUMPXCF None Using the Unicenter CA XCOM Data Transport MODIFY Commands Command Security Requirements The use of the command requires that the command s issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level
207. ata being transferred If the file is indexed the records with matching keys are replaced and those with non matching keys are added When transferring a partitioned data set specify C only if the PDS itself is being created If a new member is being sent to an existing PDS specify for Replace If you do not override the default value and the file already exists on the target system the transfer terminates with an error Default C reate Send MVS File To Another System Screen Record Separators Specifies whether Unicenter CA XCOM Data Transport adds a record separator to delimit logical records Note Skip this field unless you are sending data to an ASCII computer Value Definition Y Unicenter CA XCOM Data Transport adds a record separator such as a line feed and carriage return to delimit logical records N Unicenter CA XCOM Data Transport does not add record separators Default N EBCDIC Binary ASCII Indicates the type of transferred data The receiving computer is responsible for performing any necessary conversion Value Definition B Indicates binary data E Indicates that the data is in EBCDIC code A Indicates that the data is in ASCII code Default E The Menu Interface TSO ISPF Panels 2 25 Send MVS File To Another System Screen Truncate Record Code Table 2 26 User Guide Specifies how records exceeding the maximum logical record length LRECL are to be handled Value Definit
208. ation 0010 12 Emulators 0008 13 Installation use 0004 14 Installation use 0002 15 Installation use 0001 16 Installation use 0000 None For Unicenter CA XCOM Data Transport use only Notes The console routing codes are selected by the bit configuration where bit 0 corresponds to routing code 1 bit 1 to routing code 2 and so on These codes are assigned to messages ending with I Specifying IROUT 0000 in the Default Option Table or as part of the PARM field of the EXEC JCL statement causes the suppression of all XCOMMmnnnnl messages with the exception of XCOMM0056I and XCOMM0001I from the SYSLOG and most informational messages generated by XCOMJOB messages continue to be a part of the Unicenter CA XCOM Data Transport log Default 4020 LIST LOG PARM Parameters Broadcasts the file transfer to all remote destinations designated on a predefined distribution list Value Definition xxxxxxxx Specifies the name of a list of destinations to which the file is to be transferred The name can be up to eight alphanumeric characters long Notes GROUP LIST LU and IPNAME are mutually exclusive parameters One of these parameters must be coded either on the EXEC card or in SYSINO1 Coding more than one causes an error When a transfer is performed to a destination defined as a list of LUs or IP addresses the data is transferred to each LU or IP node in the list When GROUP or LIST is used the value for IPPORT
209. ation Fields 2 121 Sending Receiving System 2 122 Menu Interface Messages uo vagyeyeuqusuquququququququququququququququququququququququququsukqa 2 122 Chapter 3 The Batch Interface Special Features certet entente i ect et tert e ncn Deci Gin gly nte ge 3 2 XCOMIOB Sample GL oe Saale be ea bee Hees bogs Feels Rem ho ols pad 3 3 XCOMJOB TYPE EXECUTE 4 3 3 XCOMJOB TYPE SCHEDULE 3 3 XCOMJOB TYPESINQUIRE Samples 1 1 1 thet 3 4 DD Statements gae e Re dei de ted ede id eie de ted de ee Nen ON 3 5 XCOMJOB Parameter 01 21 1 27 3 8 PARM Paranieters sued vus xu ee uva desc eO dese Ead vegas 3 9 SXSINOT Parameters 55 UR iei ee eii LR bL UR PE SIS 3 28 SYOINOL DD Statement uy uv 222246 ouen ev aus Rye Nava yag desta e d suqu qua UR vate 3 29 General SYSINO Parameters o ii oiiaii dato beate He hh e 3 30 SYSINO1 Parameters Required 3 56 SYSINO1 Parameters Required by FILETYPE REPORT
210. ations Destinations are created using the N name and G group parameters of the RJWPS statement The N parameter must be 5 characters long The G parameter can be from 1 to 8 characters long and defaults to the value of the name parameter If the group name is 5 or more characters it is considered to define a generic destination We recommend using generic destinations because this approach is likely to significantly decrease the number of times that the JES3 INISH deck must be updated For the exact format of the JES3 definitions because parameters that are not discussed here may be required for your particular release of JES3 see the JES3 Systems Program Library Initialization and Tuning manual Note Unicenter CA XCOM Data Transport does not support RJE remote numbers or NJE node numbers as DESTIDs for either JES2 or JES3 Sample Specific Destination Definitions The following example defines a specific destination called ABCDE and a generic destination with the same name RJPWS N ABCDE CONSOLE JNAME ABCDE The following example defines two specific destinations called XCOM6 and A RJPWS N XCOM6 G A CONSOLE JNAME XCOM6 Sample Generic Destination Definition The following example defines a specific destination called AAAAA and a generic destination called XCOM6 RJPWS N AAAAA G XCOM6 CONSOLE JNAME AAAAA Examples of specific destinations that could all be designated by this one generic destination include X
211. ault Options Table is used The Menu Interface TSO ISPF Panels 2 83 Receive File From Another System Screen Remote File Name 2 84 User Guide Indicates the name of the file on the remote system that is being retrieved Required Value Definition Up to 256 Specifies the name of the file name to be received from the alphanumeric partner system characters You may use an asterisk as a wildcard to retrieve multiple members of a partitioned data set Specifying an asterisk for the member name will retrieve all members of a PDS for example SURVEYS To retrieve all members beginning with a specific prefix specify the prefix followed by an asterisk For example NAMES PDS AL requests that members AL ALEX ALICE and so on be transferred If no member name is entered for a partitioned data set a Member Selection List screen will be displayed allowing the selection of one or more members for transfer For more information see Member Selection List in this chapter In the VAX VMS environment brackets are used to indicate the directory in a complete file name specification However some EBCDIC environment keyboards do not provide brackets In such cases use braces instead because Unicenter CA XCOM Data Transport will convert the braces to brackets Note If the file name is longer than 59 characters enter only a plus sign in the first position of this field Upon entering this value and completing all th
212. ber When transferring a text file to a partner that supports record separators for example CRLF OD0A on Windows 2000 2003 or XP and LF 0A on UNIX record separators will be inserted No separators are inserted in binary files transferred with PACK LENGTH CRLF Specifies that the records are to be packed into blocks separated by a C arriage R eturn L ine F eed byte sequence Notes PACK LENGTH with MAXPACK 31744 should be selected when using Unicenter CA XCOM Data Transport over TCP IP If PACK LENGTH is coded then you must also code RECSEP NO Platforms that understand PACK LENGTH are IBM s AS 400 UNIX based systems and z OS systems See the appropriate documentation for the platform to see if this value is supported CRLF packing can be used with text files only It is also used when communicating with older releases of Unicenter CA XCOM Data Transport on PC DOS and OS 2 Transfer User Data System User Data Submit Job To Another System Screen Allows the user to specify up to 10 bytes of any type of data to be associated with the transfer request The user data is sent to all user exits and written to the history file upon completion of the file transfer Value Definition Up to 10 alphanumeric Specifies data to be associated with the transfer characters request Allows the specification of transfer dependent user data This data is available to user exits in the RRDSUSER field of the RRDS data area mapped by
213. bsections 3 28 User Guide General SYSINO1 Parameters This section discusses parameters that can be specified in any batch job SYSINOI Parameters Required by FILETYPE FILE This section discusses parameters that must be used when FILETYPE FILE is coded in the SYSINO1 DD statement SYSINOI Parameters Required by FILETYPE REPORT This section discusses parameters that must be used when FILETYPE REPORT is coded in the SYSINO1 DD statement SYSINO1 Tape Parameter This section discusses parameters that need to be used when tape data sets are being transferred SYSINO1 DCB Parameters This section discusses parameters that are used to allocate space for transferred data SYSINOI Transfer Control Parameters This section discusses parameters associated with Unicenter CA XCOM Data Transport s transfer control feature which is concerned with the control of multiple interdependent transfers Note There no special parameters required for FILETYPE JOB SYSINO1 Parameters SYSINO1 DD Statement The SYSINO1 parameters passed to Unicenter CA XCOM Data Transport may be coded either directly in the SYSINO1 input stream or indirectly in a data set that is referenced by the SYSINO1 DD statement The latter method that is using the SYSINO1 DD statement only to reference the data set where the transfer control parameters are coded is preferable for transfer jobs run regularly with the same processing opti
214. c the value of the APPLSEC parameter in the Default Options Table m data the data to be passed to the exit routine Operation and Control 6 25 Using the Unicenter CA XCOM Data Transport MODIFY Commands HOLD Command Format Operands Notes Holds a pending file transfer F XCOM HOLD nnnnnn The following operand is used for the HOLD command Operand Description nnnnnn Specifies the number 0 to 999999 of the transfer request that is to be held This command holds the pending file transfer request whose request number is nnnnnn provided it has not yet commenced executing Otherwise it is ignored To release a previously held request use the RELEASE command Command Security Requirements 6 26 User Guide The use of the command requires that the security authorization for the command issuer contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec HOLD destname ownername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination involved in the transfer m ownername the user ID under whose security authorization the transfer is performed INQ Command Format Operands Notes Using the Unicenter CA XCOM Data Transport MODIFY Commands Displays the current parameter definitions for MAXTASK MAXLOC MAXREM and TCPSESS
215. can also use ILUs NCP also supports ILUs over a token ring through the TIC Direct Sessions with a Dependent Logical Unit PU Type An independent logical unit can have an LU 6 2 session with a dependent LU This allows for direct sessions from an AS 400 to a VAX VMS over the SNA background network even though the VI AM is PU Type 2 0 In this environment the VTAM LOGAPPL parameter and the VTAM VARY NET LOGON command will not work Note The ILU must initiate the session it must send to the BIND When using ILUs with VTAM and Netview displays VTAM will show the PU type in its status display PU Type 2 or PU Type 2 1 PUs originally appear as PU 2 0 Once they become active they display as PU 2 1 About SNA Logical Units 5 Appendix History and SMF Files This appendix describes the Unicenter CA XCOM Data Transport SMF record the Unicenter CA XCOM Data Transport History File and the XCOMUTIL utility which selectively purges records from the History File SMF Record and History File This section describes the SMF record and History File as they are used by Unicenter CA XCOM Data Transport for z OS When Records Are Written Unicenter CA XCOM Data Transport writes an SMF record when SMF YES is specified in the Unicenter CA XCOM Data Transport Default Options Table see the chapter Configuring and Customizing Unicenter CA XCOM Data Transport for z OS in the Unicenter CA XCOM Data Transport for z OS Admi
216. cluster Therefore in order to reclaim the space follow these steps 1 Copy the history file to a sequential file 2 Run XCOMUTIL against this sequential file to purge a specified range of records and create a new sequential file Delete the existing history file and create a new one 4 Copy the new sequential file to the history file Note The Unicenter CA XCOM Data Transport server cannot be executing when XCOMUTIL is used User Guide XCOMUTIL Parameters XCOMUTIL Parameters AGE There are three parameters that control the processing performed by XCOMUTIL These parameters are input to XCOMUTIL through a SYSIN file Their description follows Specifies the number of days of history records that are retained when a purge procedure is executed Value Definition 1 to 999 Indicates the number of days of history records to be retained when executing a purge Notes After XCOMUTIL has been run the history file will comprise the current date s records plus days of records For example if the current Julian date is 02300 and AGE 1 is specified then XCOMUTIL will purge any history records written on or before 02298 Only the current and previous day s history records are saved Use the AGE parameter if you intend to run XCOMUTIL on a periodic basis It allows you to set up a procedure in which a specific date does not have to be continually modified This parameter is mutually exclusive with the DATE para
217. code table to be used by the remote partner The Menu Interface TSO ISPF Panels 2 89 Receive File From Another System Screen Pack Data Records Transfer User Data 2 90 User Guide Specifies whether record packing is to be used on a file transfer Value Definition NO Specifies that no record packing is used The data are sent unblocked LENGTH Specifies that the records are to be packed into fixed size data transfer blocks Each record begins with a 2 byte long prefix that indicates the length of the record and determines how many records can be packed into a block The default block size is 2K but it can be increased to 31K by using the MAXPACK parameter in the Unicenter CA XCOM Data Transport Default Options Table or in the Unicenter CA XCOM Data Transport control library member CRLF Specifies that the records are to be packed into blocks separated by a C arriage R eturn L ine F eed byte sequence PACK LENGTH with MAXPACK 31744 should be selected when using Unicenter CA XCOM Data Transport over TCP IP If PACK LENGTH is coded then you must also code RECSEP NO Platforms that understand PACK LENGTH are IBM s AS 400 UNIX based systems and z OS systems See the appropriate documentation for the platform to see if this value is supported CRLF packing can be used with text files only It is also used when communicating with older releases of Unicenter CA XCOM Data Transport on PC DOS and OS 2 Allows the user to spec
218. comes eligible for execution Notes You can also set the time for the future in terms of its separation in hours and minutes hhmm from the current time For example if a transmission is to start no earlier than 2 p m STARTTIME 1400 Or if the start time is two hours from now STARTTIME 0200 Default Current time STORCLAS Specifies the one to eight character name of the storage class for a new SMS managed data set Note This parameter applies only to mainframe SMS data sets Default None 3 52 User Guide SYSUDATA TDUDATA TRUNCATE SYSINO1 Parameters Allows the specification of transfer dependent user data This data is available to user exits in the RRDSUSER field of the RRDS data area mapped by the RRDDSECT macro while the transfer is pending or active The RRDSUSER field is defined by HDRDSECT within RRDDSECT Value Definition 1 to 10 bytes Specifies up to 10 bytes of data available to user exits during a file transfer Allows the specification of transfer dependent user data This data is available to user exits in the RRDXUSER field of the RRDS data area mapped by the RRDDSECT macro while the transfer is pending or active The RRDXUSER field is defined by HDRDSECT within RRDDSECT Value Definition 1 to 10 bytes Specifies up to 10 bytes of data available to user exits during a file transfer Tells Unicenter CA XCOM Data Transport how to respond to records in the source file that
219. connection and should be handled as a regular file transfer Specifies the interval at which Unicenter CA XCOM Data Transport takes a checkpoint to be used to restart a suspended or failed file transfer The length of the checkpoint interval is measured in terms of a number of blocks Value Definition 0 Specifies that Unicenter CA XCOM Data Transport is to take no checkpoints 1to9999 Specifies the number of blocks that form a checkpoint interval A checkpoint is taken whenever the specified number of blocks has been transferred Note If record packing is not used 1 record 1 block Notes Each time a checkpoint is taken the output buffers on the receiving system are written to the disk Making the checkpoint interval too short will slow down file transfers making it too long will increase the risk of data loss It is recommended that the Checkpoint Count be set to at least 1000 On Token Ring Ethernet and other high speed networks the Checkpoint Count should be set to the highest allowable value If the receiving system is z OS or VSE the Checkpoint Count should be a multiple of the blocking factor For example if the DCB attributes are RECFM FB LRECL 80 BLKSIZE 8000 the Checkpoint Count should be a multiple of 100 The Menu Interface TSO ISPF Panels 2 27 Send MVS File To Another System Screen Compression Mode 2 28 User Guide Specifies whether Unicenter CA XCOM Data Transport compresses the data being transferr
220. control functions through the Unicenter CA XCOM Data Transport Operator Control screen To send a blank parameter value to the source system enter inserting at least one blank space between the quotation marks Do this when the source system supplies its own default value for the user ID under whose access privileges the file transfer is to execute on the source system Default TSO user ID The Menu Interface TSO ISPF Panels 2 95 Receive File From Another System Screen Tape Password 2 96 Indicates whether the local data set resides on magnetic tape Value Definition Y Specifies that the local data set resides on magnetic tape N Specifies that the local data set does not reside on magnetic tape Notes If you enter Y in the Tape field a new screen MVS Extended Tape Parameter Entry is displayed allowing tape related information to be specified See MVS Extended Tape Parameter Entry Screen earlier in this chapter Default N Specifies the password associated with the local User ID parameter Value Definition Up to 31 Specifies the password associated with the local user ID alphanumeric parameter characters Notes The value entered in this field is not displayed User Guide Notify User Volume Receive File From Another System Screen Identifies the user on the receiving system Unicenter CA XCOM Data Transport is to notify once the transfer completes Value Definition LOG Indicates that the
221. croll keys PF7 scroll up and 8 scroll down or the LOCATE command discussed later in this chapter in Using the LOCATE Command For detailed information about the transfer enter S or D in the S field and press ENTER The Menu Interface TSO ISPF Panels 2 113 Unicenter CA XCOM Data Transport Transfer Request Display Screen Using the LOCATE Command 2 114 User Guide If you know some identifying attributes for a particular file transfer you can use the LOCATE command to position the display at that file transfer Enter a command of the following format on the COMMAND INPUT line LOC attribute label identifier Provide only one attribute label for each LOC entry The allowable attribute labels are as follows m DATE start date LOCFILE LFILE or LF local data set m REMFILE or RF remote data set a REMOTE REMSYS RSYS RMT remote system name a REQNUM or RNUM request number m TIME start time m USER ID or UID local user ID m XFERID or XID transfer ID For example to locate a file transfer with the request number 70342 enter the following LOC RNUM 70342 The display will be repositioned so that the file transfer whose request number is 70342 appears as the first entry on the screen The identifier of the LOCATE command can also contain a wildcard character asterisk representing any character sequence For instance the LOCATE command LOC XID BOY will cause Unicenter CA XCO
222. d is left blank the port value specified in the Unicenter CA XCOM Data Transport Default Options Table is used Specifies whether to use an OpenSSL socket or non OpenSSL socket for transfers Value Description YES Performs a secure transfer The transfer uses an OpenSSL socket and must to connect to an SSL listener on the remote partner NO Performs a non secure transfer The transfer uses a non OpenSSL socket Default NO Specifies the HFS SSL configuration file path and file name Value Definition 1 to 256 Specifies the HFS path and file name of the SSL configuration file characters used by Unicenter CA XCOM Data Transport for secure transfers Note A sample SSL configuration file configssl cnf is provided with the installation Default None The Menu Interface TSO ISPF Panels 2 7 The Primary Option Menu SNA LU Name XCOM Group Name 2 8 User Guide Specifies the logical unit name of the remote system with which a transfer is to take place Value Definition xxxxxxxx Specifies up to eight alphanumeric or national characters representing the logical unit name of the remote system with which a transfer is to take place The first character cannot be numeric Notes This parameter is mutually exclusive with IP Name XCOM Group Name Login User Name and XCOM List Name one of the five must be specified for each file transfer request Sends this file transfer to the first available LU of a group of lo
223. d to a non z OS partner it is recommended that all DCB related parameters be coded in the 5 01 stream Defines the block size of the file Value Definition 0 to 99999 Specifies a value 0 to 99999 indicating the block size of the file Notes If a receive request originates from a non z OS partner the BLKSIZE should be coded explicitly The value of the parameter must be based on a reasonable estimate Default BLKSIZE of the z OS data set if a send or receive request of any type originates from a z OS partner LRECL RECFM SYSINO1 Parameters Defines the logical record length of the file Value Definition 0 to 99999 Specifies a value 0 to 99999 representing the logical record length of the file Notes If a receive request originates from a non z OS partner the LRECL should be coded explicitly The value of the parameter must be based on a reasonable estimate Default LRECL of the z OS data set if a send or receive of any type request originates from a z OS partner Specifies the z OS record format associated with a data set This parameter uses the same format as the z OS JCL parameter Value Definition F Fixed FA Fixed ASA FB Fixed Blocked FBA Fixed Blocked ASA FBM Fixed Blocked Machine FBS Fixed Blocked Standard V Variable VA Variable ASA VB Variable Blocked VBA Variable Blocked ASA VBM Variable Blocked Machine VBS Variable Blocked Spanned VS Variable Spanned U Undef
224. ddress Session establishment is subject to a time out limit defined on the TIMEOUT parameter See the description of TIMEOUT later in this section The Batch Interface 3 37 SYSINO1 Parameters HOLD 3 38 User Guide Prevents a TYPE SCHEDULE transfer from starting until explicitly released Value Definition YES This transfer is not initiated until it is released in one of the following ways m Through the Menu Interface with a RELEASE command m Through the XTC facility NO This transfer is not held Default NO Associates a descriptive identifier with this file transfer Value Definition XXXXXXXXxx Identify the file transfer using one to ten alphanumeric or national characters Notes The ID complements the request number assigned to every locally initiated file transfer This ID appears before the message on the Unicenter CA XCOM Data Transport message log and after the message when it is displayed on a console The ID is passed to remote systems and is displayed in the remote system Unicenter CA XCOM Data Transport log For version 1 type transfers an ID of REMOTE is always assigned to this transfer on the remote system Default The job name of the job used to invoke the batch interface SYSINO1 Parameters INQWAIT Identifies how long Unicenter CA XCOM Data Transport should wait in hours minutes and seconds hhmmss before determining and reporting the status of a transfer reque
225. default is 16 Notes This feature has no effect once the transfer begins executing Do not confuse it with EPRTY the execution priority Default 16 Specifies the date when the transfer is to begin The transfer start date can be provided in one of three formats m yyyymmdd where yyyy is a 4 digit designation for a year for example 2004 mm is a 2 digit designation for one of the twelve months of the year as shown in the following chart 01 January 02 February 03 March 04 April 05 May 06 June 07 July 08 August 09 September 10 October 11 November 12 December dd is a 2 digit number in the range 01 31 designating a day of the month Example STARTDATE 20040201 schedules a transfer to begin on February 1 2004 m yyddd Julian date where yy is a 2 digit designation for a year for example 02 ddd is a 3 digit number in the range 001 366 designating a day of the year Example STARTDATE 04032 schedules a transfer to start on the 32nd day of 2004 which is the same as February 1 2004 The Batch Interface 3 51 SYSINO1 Parameters m nnn days from today where nnn is a number in the range 1 to 999 Example Specifying STARTDATE 31 on January 1 2004 schedules a transfer to begin on February 1 2004 Default Current date STARTTIME Specifies the time hhmm this transfer becomes eligible for execution Value Definition 0000 to 2400 Specifies the time hhmm this transfer be
226. defaults come from the parameter fields of the Send MVS File To Another System screen m If the data set does not exist and the File Allocation Information screen is not used the defaults come from the Unicenter CA XCOM Data Transport Default Options Table Supported File Types Unicenter CA XCOM Data Transport supports the creation of partitioned data sets and generation data groups For more information see the chapter Processing Different File Types Screen A sample File Allocation Information screen follows 04 10 26 Unicenter CA XCOM r11 5 00 TURKIO1 File Allocation Information Data set Name NA1KT50 PROG C Volume Blank for authorized default volume Unit Generic group name or unit address Space Units BLKS TRKS or CYLS Primary Quantity In above units Secondary Quantity In above units Directory Blocks Zero for sequential data set Record Format Record Length Block Size Data Class Blank for default data class Management Class Blank for default management class Storage Class Blank for default storage class Dataset Name Type LIBRARY PDS or blank c 2002 Computer Associates Inc 1 3 End 11 1 COMMAND gt F1 Help F2 SPLIT F3 End F4 RETURN F5 RFIND F6 RCHANGE F7 UP F8 DOWN F9 SWAP F10 Language F11 Hold F12 Alloc 2 42 User Guide Parameter Fields Data set Name Volume Serial Generic Unit Space Units File Allocation Information Screen The parameter fields of the File
227. ding file transfer queues JOBNAME JOB ACCOUNTING XCOM INSTALLATION CLASS A MSGCLASS X MSGLEVEL 1 1 II ICI CII IF K DOC THIS JOB BUILDS THE ACTIVE AND PENDING FILE TRANSFER QUEUE LH NOTE 1 REPLACE THE JOB CARD WITH ONE THAT IS VALID FOR YOUR SITE 2 CHANGE ALL OCCURENCES OF VVVVVV WITH A VALID DASD VOLSER NUMBER FOR VSAM FILES AT YOUR INSTALLATION 3 CHANGE ALL OCCURENCES OF XCOM X TO A VALID VSAM DATA SET PREFIX FOR YOUR INSTALLATION 4 RECSZ CHANGED FROM RECSZ 1100 1100 TO RECSZ 2020 2020 OO OK ICI IIS ICI II ICI II S1 EXEC PGM IEBDG SYSPRINT DD SYSOUT OUTPUT DD DSN amp amp TEMP UNIT SYSALLDA SPACE TRK 1 DCB RECFM FB LRECL 2020 BLKSIZE 2020 DISP NEW PASS SYSIN DD DSD OUTPUT OUTPUT FD NAME FIELD1 LENGTH 8 STARTLOC 1 PICTURE 8 XCOMRRDS FD NAME FIELD2 LENGTH 4 STARTLOC 9 PICTURE 4 B 1000 CREATE QUANTITY 1 NAME FIELD1 FIELD2 FILL X 00 752 EXEC PGM IDCAMS REGION 1024K SYSPRINT DD SYSOUT INPUT DD DSN amp amp TEMP DISP OLD DELETE SYSIN DD Sample Files 1 Sample JCL VSAM Request Queue Member DEFRRDS DELETE XCOM X RRDS SET MAXCC 0 DEF CLUST
228. ding without limitation any implied warranties of merchantability fitness for a particular purpose or noninfringement In no event will CA be liable to the end user or any third party for any loss or damage direct or indirect from the use of this documentation including without limitation lost profits business interruption goodwill or lost data even if CA is expressly advised of such loss or damage The use of any product referenced in this documentation and this documentation is governed by the end user s applicable license agreement The manufacturer of this documentation is Computer Associates International Inc Provided with Restricted Rights as set forth in 48 C F R Section 12 212 48 C F R Sections 52 227 19 c 1 and 2 or DFARS Section 252 227 7013 c 1 ii or applicable successor provisions O 2005 Computer Associates International Inc All trademarks trade names service marks and logos referenced herein belong to their respective companies Contents Chapter 1 Introduction Invoking Unicenter CA XCOM Data 1 1 Menu Interface gt dese ested RR E tees suspended eeu sade RR AUC ease KU e a quee 1 1 Batch Command Line Interface 4 1 1 Programming ntertate u os acs Reste toe shaun Ses Soe atasi S hoes bots Soe SOG Se See dut 1 2 Unicenter CA XCOM Data Transport Connectivi
229. dress of PSODSECT R2 to R12 Undefined R13 Address of register save area R14 Return address R15 Entry point address 0 4 User Guide Registers at Exit Valid Return Code Sample Program The following registers are available at exit Register Description RO to R14 Undefined R15 Return code The only valid return code is 0 for a normal return There is no sample program provided for USER EXIT 2 User Exit 2 User Exits D 5 User Exit 3 User Exit 3 Purpose This exit allows the execution of a user developed exit routine that extracts additional information from JES3 control blocks information not extracted by the XCOMPSOI module Module Name and Entry Point The module name and entry point for this exit is XCOMEX03 How to Enable Specify EXIT03 YES in the Default Options Table to enable this exit Calling Module The module XCOMPSOI calls this exit Entry Method This exit is a branch entry Required DSECT PSODSECT is the required DSECT Addressing Mode at Entry The addressing mode at entry is 31 Registers at Entry The following registers are available at entry Register Description RO Undefined R1 Address of PSODSECT R2 to R12 Undefined R13 Address of register save area R14 Return address R15 Entry point address D 6 User Guide Registers at Exit Valid Return Code Sample Program The following registers are available at exit Register Description RO to R14 Undefined R15 Return code Th
230. e fields of the screen the Extended Remote File Name Entry screen will be displayed This screen accepts file names of up to 256 characters For more information see Extended Remote File Name Entry Screen Program Library Create Add Replace Receive File From Another System Screen Informs Unicenter CA XCOM Data Transport how to handle the file that is being transferred to the remote system Value YES NO Definition Tells Unicenter CA XCOM Data Transport to transfer the file as a PDSE program library This parameter is the equivalent to PROGLIB YES in SYSINO1 Tells Unicenter CA XCOM Data Transport that the file does not involve a PDSE program library and should be handled as a regular file transfer Note There is no default value for this parameter Unless YES is specified the file is handled as a regular transfer Informs Unicenter CA XCOM Data Transport how to handle the file in which the transferred data are going to be received This is the file whose name appears in the Local File Name field Value C reate A dd R eplace Notes Definition Unicenter CA XCOM Data Transport attempts to create allocate a new file on the receiving system For information concerning the provision of additional allocation parameters for this new file see the File Allocation Information screen in this chapter Unicenter CA XCOM Data Transport adds the records being transferred to the end of an existing file named i
231. e SYSINO1 DD statement These two sets of parameters are known as PARM parameters and SYSINO1 parameters A few batch interface parameters have a dual status and can be specified both in the PARM field and the SYSINO1 DD statement However if a parameter is used as a PARM and a SYSINO1 parameter in the same XCOMJOB JCL its use in the SYSINO1 statement takes precedence over its use in the PARM field Likewise parameter s specification in the Unicenter CA XCOM Data Transport control library CAL CINBOCTL overrides its PARM field specification PARM parameters on the other hand override their counterparts in the Default Options Table which is the lowest level in the hierarchy of the Unicenter CA XCOM Data Transport parameter categories In the following sections the PARM parameters and the SYSINO1 parameters described PARM Parameters PARM Parameters ACBNAME This section describes the PARM parameters which are specified in the PARM field of the EXEC statement Identifies the VTAM ACBNAME opened by Unicenter CA XCOM Data Transport Value Definition xxxxxxxx Specifies up to eight alphanumeric characters that identify the VTAM ACBNAME Notes If the ACBNAME is seven or eight characters Unicenter CA XCOM Data Transport assumes it is an exact name If it is six characters or less Unicenter CA XCOM Data Transport assumes it is a generic name and appends a two digit numeric suffix from 00 to 99 This suffix is derived
232. e Socket SSL Informs Unicenter CA XCOM Data Transport how to handle the security of the transfer to the remote system Value Definition YES Tells Unicenter CA XCOM Data Transport to use OpenSSL for the transfer of the file and that it must connect to a SSL port on the remote partner NO Tells Unicenter CA XCOM Data Transport that the file does not require a secure connection and should be handled as a regular file transfer Remote System Identification Indicates the remote destination where the file is to be sent Value Definition SNA destination name Specifies the SNA name of the remote system where the transfer is directed 1 to 8 characters Group name Specifies the name of a destination member defined in the Unicenter CA XCOM Data Transport Control Library This member can contain a single SNA LU name or TCP IP name or address or up to 16 SNA LU names 1 to 8 characters List name Specifies a list of SNA LU names and or TCP IP addresses 1 to 8 characters Login user name Specifies a user ID on the source computer whose access privileges are used to execute the file transfer 1 to 8 characters IP destination name Specifies the IP destination name of the remote system where the transfer is directed 1 to 63 characters nnn nnn nnn nnn Specifies the IP address of the remote system where the transfer is directed The Menu Interface TSO ISPF Panels 2 51 Send Report To Another System Screen
233. e description of the parameter LIST in the section PARM Parameters Interdependent Transfers Unicenter CA XCOM Transfer Control referred to as processing makes use of transfer parameters allowing interdependent transfers to be defined as single group Transfers in the same group can be held purged or released depending on the successful or unsuccessful completion of other transfers in the group For important information about XTC processing see the sections SYSINO1 Transfer Control XTC Parameters and Coding Interdependent Transfers User Specified Checkpoints For important information about user specified checkpoints see the description of the parameter CKPT in the section General SYSINO1 Parameters Batched Multiple Transfers For important information about batched multiple transfers see the description of the parameters CONTINUE in the section PARM Parameters and NEWXFER in the section General SYSIN01 Parameters 3 2 User Guide XCOMJOB Sample JCL XCOMJOB Sample JCL The Unicenter CA XCOM Data Transport samples library contains the following sample XCOMJOB job streams Type of Request Name of the Sample Job TYPE EXECUTE CAI CINBOSAM XCOMJOBE TYPE SCHEDULE CAI CINBOSAM XCOMJOBS CAI CINBOSAM XCOMJOXS for XCOMPLEX Admin Server TYPE INQUIRE CAI CINBOSAM XCOMJOBI CAI CINBOSAM XCOMJOXT for XCOMPLEX Worker Server Copies of these sample job streams are provided in the appendix
234. e direct spool interface in either of two ways m Submit jobs through z OS internal reader m Write to a partitioned transient data set that is OSAM file for the JCL to direct to one of the remote destinations If this method is used to send multiple files to the same remote destination the transient data queue sequential file must be closed and reopened between the writing of each file 5 6 User Guide Basics of JES Spool Use Using Process SYSOUT with TSO TSO users can take advantage of the direct spool interface by using any command that permits the allocation of a SYSOUT file to a JES destination For example some newer versions of TSO allow specification of the DEST operands with the ALLOCATE command On TSO systems with the PRINTOFF command destinations can be specified on the command line TSO users can also requeue a data set to a specific destination Sample z OS File Transfer to a PC In this example the sequential file HOST SEQ FILE is sent to a personal computer The sample destination name is PCLOBBY Note This destination name must be a valid destination name to both Unicenter CA XCOM Data Transport and JES MYJOB JOB 453W XCOM DEMO MSGCLASS A CLASS J STEP1 EXEC PGM IEBGENER SYSPRINT DD SYSOUT A SYSIN DD DUMMY SYSUT1 DD DISP SHR DSN HOST SEQ FILE SYSUT2 DD SYSOUT A DEST PCLOBBY Sample z OS File Transfer to a VAX In this example there is an application program located i
235. e only valid return code is 0 for a normal return There is no sample program provided for user exit 3 User Exit 3 User Exits D 7 User Exit 4 User Exit 4 Purpose This exit allows the execution of a user developed exit routine that provides security checking for the Unicenter CA XCOM Data Transport TSO ISPF Operator Control Facility Module Name and Entry Point The module name and entry point for this exit is XCOMEX04 How to Enable Specify EXITO4 YES in the Default Options Table to enable this exit Calling Module The modules XCOMDPJ XCOMDSPL and XCOMOPER call this exit Entry Method This exit is a branch entry Required DSECT ADMPL is the required DSECT Addressing Mode at Entry The addressing mode at entry is 31 Registers at Entry The following registers are available at entry Register Description RO Undefined R1 Address of ADMPL R2 to R12 Undefined R13 Address of register save area R14 Return address R15 Entry point address D 8 User Guide Registers at Exit Valid Return Code Sample Program User Exit 4 The following registers are available at exit Register Description RO to R14 Undefined R15 Return code The following return codes are valid for user exit 4 Return Code Description 0 User is authorized to perform function 8 User is NOT authorized to perform function The following is a sample program using this exit CAI CINBOSAM XCOMEX04 User Exits D 9 User Exit 5 User Ex
236. e used for executing the transfer Notes If the remote system does not perform security checking you can skip this and the Remote Password parameter To send a blank parameter value to the remote system enter inserting at least one blank space between the quotation marks Do this when the source system supplies its own default value for the user ID under whose access privileges the file transfer is to execute on the source system Default None Indicates whether the remote data set resides on magnetic tape Value Definition Y Specifies that the remote data set resides on magnetic tape N Specifies that the remote data set does not reside on magnetic tape Notes If you enter Y in the Tape field a new screen MVS Extended Tape Parameter Entry see next section is displayed allowing tape related information to be specified Default N The Menu Interface TSO ISPF Panels 2 31 Send MVS File To Another System Screen Password 2 32 User Guide Identifies the password associated with the remote user ID Value Definition Up to 31 Specifies up to 31 alphanumeric characters representing the alphanumeric user password associated with the user ID characters Notes This field is not displayed If the remote system is running IBM RACF eTrust CA ACF2 Security or eTrust CA Top Secret Security this parameter can be used to change the password on the remote system To do this use the following format
237. eature Process SYSOUT 5 5 Basics of JES Spool Use Assigning a JES Destination or Writer to a Remote Computer The Unicenter CA XCOM Data Transport Destination Table associates JES destinations with remote computers a VTAM logical unit LU name IP address or group of logical units This table is created when Unicenter CA XCOM Data Transport is installed and can be modified at any time by using the Unicenter CA XCOM Data Transport Destination Tables For more information see the chapter Configuring and Customizing Unicenter CA XCOM Data Transport in the Unicenter CA XCOM Data Transport for z OS Administrator Guide You can use JES to create Destination Table entries by updating the JES initiation parameters according to whether the host computer is running JES2 or JES3 For more information see JES2 Considerations and JES3 Considerations in this chapter Assigning a JES Destination or Writer to a Specific User The assignment TYPE USER in the Unicenter CA XCOM Data Transport Destination Table allows a JES destination or writer to be routed to a specific user When that user logs on to Unicenter CA XCOM Data Transport all output queued to the destination or writer specified in the user definition member is sent out on the session Note This Unicenter CA XCOM Data Transport feature is not supported for TCP IP destinations Using Process SYSOUT with CICS or Other Online Systems With CICS or other online systems you can use th
238. ections Section Dependent on transfer type Common information No Sending system information Yes Receiving system information Yes 2 118 User Guide Common Section Information Fields Detailed File Transfer Display The common section contains detailed information and statistics pertaining to a file transfer request The information contained in this section is common to all file transfer requests Common Section Field Heading Line Sched Start Time Transfer ID End Time Last Action Status Priority Sel Exec Compression Mode Transfrd Records Bytes Compress Bytes Explanation The heading line of the display describes the type of file transfer request SEND RECEIVE FILE REPORT JOD the request number associated with the request and the day date and time that the request was queued The day date and time that the transfer is or was scheduled to begin The transfer ID that was entered with or assigned to the request If the transfer completed successfully or unsuccessfully this field contains the day date and time that the transfer ended This field is not currently used The status of the request For a definition of the possible entries in this field see Status Fields in this chapter The selection and execution priorities assigned to the transfer The compression method used The number of records transferred The total number of bytes transferred The number of bytes
239. ecure Socket Layer SSL be used to perform secure TCP IP transfers between platforms running Unicenter CA XCOM Data Transport r11 and above that support secure SSL TCP IP A secure SSL TCP IP transfer allows for the encryption of the transmitted data and adding a digital signature to the encryption of the transmitted data Advantage CA XCOM Data Transport uses OpenSSL to implement a secure TCP IP transfer Secure SSL TCP IP support is provided between the following platforms m Linux S 390 m Linux x86 Windows NT family 2000 2003 and XP m z OS m Most common UNIX platforms Unicenter CA XCOM Data Transport Nodes in the TCP IP Network TCP IP Address 1 10 User Guide Each computer in a TCP IP network is assigned at least one unique address which is used by the IP and other higher level protocols TCP IP employs an addressing scheme consisting of a 32 bit long field divided into two parts The first part of the address field contains a network address the second field contains the address of a specific computer A TCP IP address is written in dotted decimal notation which is obtained by first dividing the 32 bit long address into four 8 bit long fields and then converting each of the four fields into a decimal number and separating the fields with dots or periods TCP IP Port Successful Send File Transfer Scenario Instead of using a numeric address a symbolic name may be used to identify a computer in a TCP
240. ed Tape Parameter Entry The parameter fields of the MVS Extended Tape Parameter Entry screen are described in the following Specifies whether the remote local data set resides on tape Value Definition YES Indicates that the data set resides on tape NO Indicates that the data set does not reside on tape Specifies the sequence number of the data set on tape Value Definition 1 to 9999999 Specifies the sequence number of the data set on tape Specifies the type of processing to be done on the tape data set Value Definition SL Specifies the tape processing type SL NL Specifies the tape processing type NL NSL Specifies the tape processing type NSL SUL Specifies the tape processing type SUL BLP Specifies the tape processing type BLP LTM Specifies the tape processing type LTM AL Specifies the tape processing type AL AUL Specifies the tape processing type AUL The Menu Interface TSO ISPF Panels 2 39 MVS Extended Tape Parameter Entry Unit Count Volume Sequence Density Volume Count 2 40 User Guide Specifies the number of units to be allocated on the system Value Definition 1 to 20 Specifies the number of the units to be allocated on the system Specifies the sequence number of the first volume of a multivolume data set to be used Value Definition 1 to 255 Specifies the sequence number of the first volume of a multivolume data set to be used Specifies the density to be used in creating a ta
241. ed and decompresses it on the remote system Compressing the data decreases the transmission time on lower speed lines Value Definition YES Provides Run Length Encoding RLE for blanks and binary zeros only NO No data compression RLE Provides complete Run Length Encoding for all characters COMPACT Provides full RLE as in RLE above plus a byte compaction scheme that is suitable for uppercase English text COMPACTL Same as COMPACT above only the compaction scheme is most beneficial for lowercase English text LZSMALL Lempel Ziv 77 compression with a small memory allocation scheme LZMEDIUM Lempel Ziv 77 compression with a medium memory allocation scheme LZLARGE Lempel Ziv 77 compression with a large memory allocation scheme HUFFMAN Greater compression than RLE but not as much as the Lempel Ziv 77 modes LZRW3 General purpose algorithm that runs fast and gives reasonable compression ZLIB n Greater compression than LZRW3 but less than LZSMALL LZMEDIUM and LZLARGE The n value can be 1 through 9 Note Not all compression modes are supported on all platforms Default YES Pack Data Records Send MVS File To Another System Screen Specifies whether record packing is to be used on a file transfer Value Definition NO Specifies that no record packing is used The data are sent unblocked LENGTH Specifies that the records to be packed into fixed size data transfer blocks Each record begins w
242. ed in asymmetrical links where one node is a slave to the host The protocol for 3270 video display stations It defines the data streams used by dumb terminals to communicate with the host This was a variant subset of 3270 protocol that was used to drive printers attached to 3274 cluster controllers Today it is still used to support old hardware This protocol was intended for use on word processors attached to a host network You may still see it on old IBM word processors Developed during the late 1970s this was SNA s prototype protocol defined for program to program communication It was a first attempt to provide a standardized mechanism for communication between intelligent peer computers About SNA Logical Units 3 Independent Logical Units Definition 6 2 Alternatively referred to by the marketing title Advanced Program to Program Communications APPC this used to be called the Convergent LU or the LU type around which the entire IBM product line would converge LU 6 2 defines standard functions or verbs such as SEND RECEIVE and CONFIRM that simplify the work of making two different programs on two different kinds of computer talk to each other Specifies the data stream of the 5250 video display stations commonly used with the IBM mid range computers Independent Logical Units 4 User Guide Unicenter CA XCOM Data Transport supports independent logical units ILUs An ILU is a logical
243. ed time out value Similarly a SEND or RECEIVE command times out if a transmission gets hung up Value Definition 0to 99999 Specifies how long Unicenter CA XCOM Data Transport should seconds wait for a VIAM or TCP IP command before terminating the program TRACE PARM Parameters Notes Unicenter CA XCOM Data Transport always queues to VTAM the request to establish the session with the remote system If TYPE EXECUTE or TYPE INQUIRE Unicenter CA XCOM Data Transport attempts to establish the session within the time specified in the TIMEOUT parameter If it cannot then the job aborts An error message is written to the Unicenter CA XCOM Data Transport log and is also sent to the operator console A return code of 9 or 10 is also issued For a TCP IP transfer the TIMEOUT parameter determines how long to wait for a connection to a remote IP node TIMEOUT should not be less than 60 seconds to allow sufficient time for a normal transfer or inquiry request to complete Default 600 Activates the internal Unicenter CA XCOM Data Transport trace function as an alternative to the VI AM trace The trace data often useful in debugging problems is sent to the SYSOUT class defined by the DUMPCL parameter Value Definition YES Use the Unicenter CA XCOM Data Transport trace function instead of the VTAM trace NO Do not use the Unicenter CA XCOM Data Transport trace function Default NO The Batch Interface 3 25 PARM Parameters
244. een allocated to the job step that executes your application program unless the local file was defined with the LFILE parameter You do not have to load the parameters in SYSINO1 before the job starts Instead you can OPEN the file for output and write the parameters to it one 80 character output record at a time This way the application program determines the parameter values Code a working storage data item for the Batch Interface routine XCOMJOB This should be an eight character alphanumeric with a VALUE clause set to Call Unicenter CA XCOM Data Transport dynamically Make your PICTURE clause large enough to accommodate the total length of your parameter data Move the length of the XCOM PARM DATA field into the XCOM PARM LEN The following is a sample fragment of a COBOL program that calls Unicenter CA XCOM Data Transport J X OEOKOIOK SAMPLE PROGRAM TO CALL XCOM STEP COMPILE SAMPLE PROGRAM STEP LKED LINK EDIT SAMPLE PROGRAM STEP RUN EXECUTE SAMPLE PROGRAM S1 EXEC COBUCL PARM COB PM COB SYSIN DD 000100 IDENTIFICATION DIVISION 000200 PROGRAM ID SAMPCOB
245. efault Options Table type the STOP command operand IMMED Operation and Control 6 43 Using the Unicenter CA XCOM Data Transport MODIFY Commands SUSPEND Command Immediately suspends an active transfer Format F XCOM SUSPEND Zuname nnnnnn Operands The following operands are used with the SUSPEND command Operand Description luname Specifies the name 1 to 8 characters of the single session SNA LU that you wish to suspend nnnnnn Specifies the request number 0 to 999999 of the transfer to be suspended This operand must be used for transfers with a TCP IP partner or with a parallel sessions SNA LU partner Notes A Version 2 transfer can be resumed from the last checkpoint taken If it does not the transfer is resumed from the beginning of the file If the transfer was initiated and suspended by a remote system the operation resumes in the next retry interval If the transfer was initiated and suspended by the local system the RESUME command must be used for the transfer to continue If multiple transfers are running with the same request number the first one shown with the DISPLAY command is the one affected by the SUSPEND command For greater control we recommend using the ISPF or CICS menu interface 6 44 User Guide Using the Unicenter CA XCOM Data Transport MODIFY Commands Command Security Requirements TERM Command Format Operands The use of the command requires that the command issuer s security
246. efinition This field is used to send data and store it as a file on a remote system This field is used to send data to a remote system and have it printed as a report This field is used to send data to a remote system and have it run as a job The Menu Interface TSO ISPF Panels 2 15 Send MVS File To Another System Screen Send MVS File To Another System Screen The Send MVS File to Another System screen provides Unicenter CA XCOM Data Transport with the necessary information to transmit an MVS data set to a target file on a remote system The data set being sent must exist as a valid data set on the local system but does not have to be cataloged 04 10 26 Unicenter CA XCOM r11 5 00 TURKIO1 Send MVS File To Another System Transfer ID Local File Name IP Name Addr 122 222 222 222 Remote File Name Remote file substitution char Program Library NO Create Replace Add C R A C Record Separators Y N N EBCDIC Binary ASCII E B A B Truncate Record Y N Code Table Remote System Information s User ID Tape Y N Password Domain Notify User Volume PFK 1 Help 3 End COMMAND gt 1 1 F2 SPLIT F3 End F7 UP F8 DOWN F9 SWAP F4 RETURN FlO0 Language F11 Hold Execution Priority Port Replaced with member name Secure Socket SSL NO Checkpoint Count Compression Mode Pack Data Records N C L Transfer User Data System User Data Local System TUR
247. ent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination for which the error flag is to be set m asterisk all destinations RESUME Command Resumes a suspended file transfer Format F XCOM RESUMe nnnnnn Operands The following operand is used with the RESUME command Operand Description nnnnnn Specifies the partner system s transfer request number 0 to 999999 of the suspended transfer that is to be resumed Notes If the transfer is a Version 2 transfer it is resumed from the last checkpoint taken when it was suspended Operation and Control 6 35 Using the Unicenter CA XCOM Data Transport MODIFY Commands Command Security Requirements RSHOW Command Format Operands 6 36 User Guide The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec RESUME destname ownername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination involved in the transfer m ownername the user ID under whose security authorization the transfer is performed Displays remotely initiated transfers F XCOM RSHOW nnnnnn destname The following operand is used with the
248. ent version of these potential problems can be avoided if the LOCAL FILE name is specified on the 01 parameter rather than with the LCLDS01 DD statement for TYPE SCHEDULE transfers Note This distinction is irrelevant to TYPE EXECUTE transfers because there is no time lag with these types of transfers The handling of Generation Data Groups by the Menu Interface see the chapter The Menu Interface TSO ISPF Panels does not involve production JCL The local file specification is interpreted literally by Unicenter CA XCOM Data Transport For queued and non queued transfers if a relative generation number is specified for the local Data set Name Unicenter CA XCOM Data Transport transfers the generation data set possessing this relative generation number whenever the transfer executes For example if you specify the current generation 0 the current generation is always processed To process a particular data set give it a GrxxxV00 suffix This data set is then processed whenever the transfer executes Transferring All Generations of a GDG If desired Unicenter CA XCOM Data Transport can transfer all generation data sets within a GDG in a single transfer operation To do so specify the GDG by its base name in the request that is without a relative generation number Unicenter CA XCOM Data Transport then transfers all data sets in a single stream starting with the newest generation and ending with the old
249. enter CA XCOM Data Transport for VSE does not support checkpoint restart for SAM jobs Remote System Information 9 25 Windows 98 Windows 98 This section contains information about important aspects of the Windows 98 operating system Naming Conventions 9 26 User Guide Unicenter CA XCOM Data Transport for Windows supports only the FAT file system for Windows Use the following format to name Windows files d N directory name N N filename ext The following table describes the parts of a Windows file name Part Description d A particular device The C drive is the most common local hard drive the A drive is the most common floppy and the F drive is the most common network drive PCs support a facility in which a section of memory RAM can also be used as a virtual disk drive In high speed link environments the performance of Unicenter CA XCOM Data Transport is directly related to the speed of the disk drive In most environments the fastest to the slowest devices are as follows disks D drive m Directly connected hard disks C drive m Network disks F drive m Floppy disks A or B drive Note If you do not specify a drive the default current drive is used This directory in Windows changes depending on the last application accessed directory name One or more optional directories which allow you to assign organization to the drive If you specify a destination file name with a directo
250. entification field is a specific destination name or a number in the case of an IP address You cannot change the destination type for instance SNA LU Name to XCOM Group Name but you can change the specific destination name or number Default The remote destination specified on the Primary Option Menu Dropsess Port Receive File From Another System Screen Specifies whether a session with a Unicenter CA XCOM Data Transport partner should be terminated at the completion of a file transfer Optional Note This field is displayed only when an SNA type of partner is referenced in the Remote System Identification field Value Definition Y Indicates that the session is to be terminated after the transfer has completed N Indicates that the session is to be retained after the transfer has completed Q Indicates that the session is to be terminated if there are no additional transfer requests for the current Unicenter CA XCOM Data Transport partner Default N Specifies the number of the IP port where Unicenter CA XCOM Data Transport listens at the remote system Note This field is displayed on the screen only when an IP name or address is referenced in the Remote System Identification field Value Definition 1 to 65535 Identifies the IP port monitored listened to by Unicenter CA XCOM Data Transport at the remote system If this field is left blank the port value specified in the Unicenter CA XCOM Data Transport Def
251. er NOTSEL indicates one of three possibilities m The member was not selected m Multiple members were selected when the Queue for Execution field was set to or defaulted to Y m Unicenter CA XCOM Data Transport has determined or assumed that the Remote File is not a partitioned data set With multiple member selection each member except the first will be marked NOTSEL Only the first member is transferred For NOTSEL values press the Help key PF1 13 to see why the member was not selected Pressing the Help key again will provide a definition of Unicenter CA XCOM Data Transport s selection criteria To exit the Member Selection List screen press the END key PF3 This will initiate the transfer request To exit the Member Selection List screen without initiating the transfer request enter CANCEL on the Command Line The Menu Interface TSO ISPF Panels 2 107 Unicenter CA XCOM Data Transport Operator Control Unicenter CA XCOM Data Transport Operator Control The File Transfer Display Select screen is the entry point for displaying a list of one or more of the following options m Inactive file transfers file transfers that have not started yet m Active file transfers file transfers that are currently in progress m Completed file transfers Use the display to view information and change the processing parameters applicable to one or more file transfers 04 10 26 Unicenter CA XCOM r11 5 00 TURKIO1 File Tran
252. er exit D 8 invoking 8 2 overview 8 1 user exit D 10 selection commands 2 117 priority 2 104 Selection menu 2 4 Send File screen local system information 2 34 parameter fields 2 16 remote system information 2 30 Send Files Selection menu option 2 5 Send Functions screen 2 14 menu options 2 14 Send Jobs Selection menu option 2 5 Send MVS File To Another System screen 2 15 send record separators Receive File From Another System screen 2 87 Send File screen 2 24 Send Report screen 2 55 Submit Job screen 2 71 Send Report screen 2 47 local system 2 63 parameter fields 2 48 remote system information 2 61 Send Report To Another System screen 2 47 Send Reports Selection menu option 2 5 sending reports with PSO 5 3 sending system information 2 122 Index 11 server Unicenter CA XCOM Data Transport starting 6 1 XCOMPLEX Admin defining C 20 XCOMPLEX Worker defining C 21 session 2 cancel from command line 6 11 cancellation operands 6 11 establishment timeout 3 25 wait time 3 24 ID A 2 SHOW MODIFY command 6 38 SID See session ID SMF files B 1 record 1 records 6 17 system parameter 6 17 MFDSECT Assembler macro B 2 S S SMENUM system parameter 6 17 SNA LU name 2 6 2 7 S network end user level 1 4 levels diagram 1 6 levels general explanation 1 4 logical level 1 5 physical level 1 5 SNAP MODIFY command 6 39
253. er job steps that transfer files The dependent steps can execute conditionally based on the return code issued by TYPE INQUIRE When you schedule a transfer you must include the INQUIRE data set in that JCL Unicenter CA XCOM Data Transport schedules the transfer and writes the request number and a time stamp into the INQUIRE data set In the INQUIRE step you must reference the same INQUIRE data set You must at least steplib to that same library in your Unicenter CA XCOM Data Transport start up JCL It is essential that the Unicenter CA XCOM Data Transport started task accesses the same maintained libraries as the INQUIRE step accesses Make sure that this library occurs first in any concatenation The INQUIRE process then interrogates the Unicenter CA XCOM Data Transport server to locate the transfer It examines the transfer requests every 10 seconds until the amount of time specified in the SYSINO1 parameter INQWAIT has elapsed See the SYSIN01 parameter INQWAIT for details If the transfer is pending or active it is listed in the Unicenter CA XCOM Data Transport RRDS If the transfer has completed whether successful or unsuccessful it is logged in the Unicenter CA XCOM Data Transport history file Both the request number and the time stamp for that transfer are used to search for the transfer The return code passed back by the INQUIRE step is determined by where the transfer was found and the actual status of the transfer TYPE INQUIRE
254. er the Japanese EBCDIC data It is accessed from all XCOM ISPF panels by pressing 10 04 10 26 Unicenter CA XCOM r11 5 00 15 005 Japanese Character Set Support Screen EBCDIC Japanese Data E or K Lower case English or Katakana in data EBCDIC Japanese Control E E or K Lower case English or Katakana in header Delete Shift D D or C Delete Shift in amp Shift out characters or convert to spaces Double byte code Local double byte character set characters or convert to spaces 0 IBM 5 PS 55 1 AX 1 1 Help 3 End 11 Hold 12 Show COMMANDS gt 1 1 F2 SPLIT F3 End F4 RETURN F5 RFIND F6 RCHANGE F7 UP F8 DOWN F9 SWAP F1 Language 11 1 F12 ALLOC Parameter Fields The parameter fields of the Japanese Character Set Support Screen are described in the following EBCDIC Japanese Data Specifies whether the data file contains Katakana characters Value Definition K The data file being transferred contains Katakana characters rather than English lower case E The data file does not contain Katakana characters Default E The Menu Interface TSO ISPF Panels 2 99 Japanese Character Set Support Screen EBCDIC Japanese Control Specifies whether the header fields contain Katakana characters Value Definition K The control information header fields being transferred contains Katakana characters rather than English lower case E The control information does not contain Katak
255. ered by relative record number The space allocated for each record is specified when the file is created Records in these files can be deleted and added again in place m Key sequenced files Key sequenced files are supported only for the Replace operation The file must already exist for Unicenter CA XCOM Data Transport to perform an action on it Remote System Information 9 15 Tandem File Type Specification Locally Initiated Send Requests Receive Requests When you send a file from the Tandem the remote Unicenter CA XCOM Data Transport determines the file type when it opens the file For locally or remotely initiated receive requests the file type must be specified by the GUARDIAN FILE TYPE parameter Use one of the following values EDIT UNSTRUCTURED ENTRY SEQ RELATIVE Remotely Initiated Send Requests 9 16 For remotely initiated transfer requests for example send file job or report use the following Record Format Guardian File Type Created F Relative FB Entry Sequence VB Edit U Unstructured Note Key sequence files are supported only if the file exists You can do a replace but not a create User Guide UNIX UNIX This section contains information about important aspects of the UNIX operating system Naming Conventions Use the following format to name a UNIX file directory subdirectoryl filename Use up to 256 characters for the entire path of the file there are no re
256. errupted transfers from the point at which the most recent checkpoint was taken Each time a checkpoint is taken the output buffers on the receiving system are written to the disk A checkpoint interval that is too short slows down file transfers a checkpoint interval that is too long increases the risk of data loss We recommend that you set the checkpoint count to at least 1000 On Token Ring Ethernet and other high speed networks the checkpoint count should be set to the highest allowable value if needed If the receiving system is z OS or VSE the checkpoint count should be set to a multiple of the blocking factor For example if the DCB attributes are RECFM FB LRECL 80 BLKSIZE 8000 the checkpoint count should be a multiple of 100 Default Taken from the Unicenter CA XCOM Data Transport default options table The Batch Interface 3 31 SYSINO1 Parameters CODE Identifies the type of transferred data The receiving computer is responsible for performing any necessary conversion Value Definition EBCDIC Indicates that the transferred data are coded in EBCDIC format ASCII Indicates that the transferred data are coded in ASCII format BINARY Indicates that the transferred data are coded in binary format Default EBCDIC Notes EBCDIC packed decimal fields cannot be transferred under EBCDIC Use BINARY to transfer EBCDIC packed decimal data If you specify CODE ASCII and the receiving computer is a mainframe then this pa
257. ers consisting of the following diphanumene A 1 to 44 character data set name characters m Anoptional member name enclosed in parentheses m Optional single quotation marks apostrophes to enclose the data set m The user s TSO profile prefix is inserted at the beginning of this entry unless the entry is enclosed in single apostrophes If the TSO profile is set to NOPREFIX nothing is inserted Notes Use an asterisk to send multiple members of a partitioned data set Specifying an asterisk for the member name will send all members of a PDS for example SURVEYS To send all members beginning with a specific prefix specify this prefix followed by an asterisk For example NAMES PDS AL requests that members AL ALEX and ALICE all be transferred The asterisk must be the last character before the right parentheses If no member name is entered for a partitioned data set a Member Selection List panel will be displayed allowing the selection of one or more members for transfer For more information see Remote File Name and Member Selection List in this chapter Default The last data set name entered Specifies the sequence number of the data set on tape Note Leave the field blank for disk files Value Definition 1109999 Specifies the sequence number of the data set on tape The Menu Interface TSO ISPF Panels 2 67 Submit Job To Another System Screen Label Type Unit Count Volume Sequence 2 68 User Guide
258. esebee 6 51 COMMANA 6 52 Chapter 7 Processing Different File Types Partitionec Data S to hase hater sa ae E E UE 7 1 PDS PDSE 2 2 2 2 24 2 7 1 PDSE Program ETE A ee neers 7 2 Contents vii Generic File Specifications Using Wildcards 7 2 Library Transfers oves eoe ovas uqu susu unu Mews Vat aUa Maa quan aM qnd a a Nau gia 7 3 Generation Data Gro ps siis lbid 4 7 3 Scheduled Versus Immediate Transfer Considerations 7 4 Batch Interface DEI 7 4 Menu Intenfae yeu ey eu susu dud ev dug a ade atu E EEA ais Vani dies Ua au did pa Red qi 7 5 Transferring All Generations ofa GDG 7 5 VOAM ntes 7 6 Key Sequenced Data Sets 5 2 0 7 6 Entry Sequenced Data Sets ESDS uq yuq ausu ga d Ua A oua 7 6 Relative Record Data Sets 5 7 6 Miscellaneou
259. ess of file data field Undefined Address of CSA control block mapped by CSADSECT macro Return address Entry point address The following registers are available at exit Register R0 to R14 R15 Description Undefined Return code The only valid return code is 0 for a normal return The following is a sample program using this exit CAI CINBOSAM XCOMEX10 User Exit 12 User Exit 12 Purpose This exit point controls partner LU security It executes a user written exit routine that verifies a given user s authority to transfer data to and from a particular LU The following are the possible results of the verification 1 The user is given access to the designated LUs 2 The user is denied access to the LUs 3 The user s right to access the LUs is referred to the security package Module Name and Entry Point The module name and entry point for this exit is 12 How to Enable Specify EXIT12 YES in the Default Options Table to enable this exit Calling Module The module XCOMTRGT calls this exit Entry Method This exit is a branch entry Required DSECT EX12PLST is the required DSECT Addressing Mode at Entry The addressing mode at entry is 31 User Exits 0 23 User Exit 12 Registers at Entry Registers at Exit Valid Return Code Sample Program D 24 User Guide The following registers are available at entry Register Description RO Undefined R1 Address of EX12PLST R2 t
260. est Processing Different File Types 7 5 VSAM Files VSAM Files Unicenter CA XCOM Data Transport supports three access methods 5 BPAM for partitioned data sets and VSAM For VSAM it supports the key sequenced data set KSDS entry sequenced data set ESDS and relative record data set RRDS file types Note Because of VSAM limitations the Unicenter CA XCOM Data Transport checkpoint restart facility is not supported for ESDS files For KSDS and RRDS files Unicenter CA XCOM Data Transport supports checkpoint restart only for file transfers using REPLACE as the specified File Option Key Sequenced Data Sets KSDS When transmitting an indexed file across systems for example a VSAM KSDS file the key length and relative key position must be the same on both the sending and receiving computers Unicenter CA XCOM Data Transport supports the insertion of new records between existing records and the replacement of existing keys for KSDS files Version 2 transfers only To do this specify ADD or REPLACE for the FILEOPT parameter You must also employ the CREATE option if the data set has been defined with the REUSE option and is to be reused Entry Sequenced Data Sets ESDS For Entry Sequenced Data sets specify ADD This adds the new input to the end of the data set You must also employ the CREATE option if the data set has been defined with the REUSE option and is to be reused Relative Record Data Sets RRDS
261. est number XRSHOW limits the display to only the XCOMPLEX Worker Servers that have the specified request number Additional details are NOT displayed For additional details enter the RSHOW command from the XCOMPLEX Worker Server The display provides information about m Requests that are active m Requests that were interrupted but are still eligible to be restarted for example requests that have not yet been completed purged or aged off the queue Important In large networks with a large number of queued transfers the output of this command can exhaust your WTO buffers Command Security Requirements 6 50 User Guide The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name READ XCOM applsec XRSHOW The applsec variable represents the value of the APPLSEC parameter in the Default Options Table Using the Unicenter CA XCOM Data Transport MODIFY Commands XSHOW Command Format Operand Notes For XCOMPLEX Admin Server only Displays information about locally initiated file transfer requests for all XCOMPLEX Worker Servers connected to the XCOMPLEX Admin Server F XCOM XSHOW nnnnnn The following is the operand for the XSHOW command Operand Description nnnnnn Specifies the number 0 to 999999 of the transfer request about which information is to be displayed If you e
262. exceed the maximum record length permitted on the target computer Value Definition YES Truncate any excess characters NO Abort the transfer Once the problem has been resolved the transfer must be rerun Default NO The Batch Interface 3 53 SYSINO1 Parameters TYPE USER USERID 3 54 User Guide Indicates whether the file transfer is inbound or outbound Required Value Definition SEND Indicates that the file transfer is outbound from this system RECEIVE Indicates that the file transfer is inbound to this system Notes If TYPE RECEIVE then FILETYPE FILE must be specified Indicates that the transfer is to take place on a session on which this user has logged onto the Unicenter CA XCOM Data Transport server Value Definition xxxxxxxx Specifies one to eight alphanumeric characters representing a user whose Unicenter CA XCOM Data Transport session is to be used for a file transfer Notes GROUP LIST USER LU and IPNAME are mutually exclusive parameters One of these parameters must be coded Identifies the user ID that Unicenter CA XCOM Data Transport is to use on the remote system The user ID must be known to the remote system s security Value Definition XXXXXXXXXX Specifies a user ID up to 12 alphanumeric characters whose access privileges on the remote computer are used for this file transfer Notes For IBM AS 400 or VAX specify the user s sign on If this parameter is omitted Unicenter CA
263. fault The last remote user ID entered Identifies the password associated with the remote user ID This value is not displayed Value Definition Up to 31 Specifies up to 31 alphanumeric characters representing the alphanumeric remote user s password characters If the remote system is running IBM eTrust CA ACF2 Security or eTrust CA Top Secret Security you can also use this parameter to change the password on the remote system by using this format oldpassword newpassword Domain Notify User Submit Job To Another System Screen Identifies the Windows 2000 2003 or XP domain associated with the remote server Value Definition Up to 15 Specifies up to 15 alphanumeric characters representing the alphanumeric domain user password and ID associated with the remote characters server Note Can be used for transfers running under Windows 2000 2008 or XP only Identifies the user on the remote system Unicenter CA XCOM Data Transport is to notify once the transfer completes Value Definition user id If any value but LOG is given Unicenter CA XCOM Data Transport interprets this as a specific user ID on the remote system If this user is not logged on when the transfer completes the message is displayed next time the user does log on LOG LOG requests that the main operator on the remote computer be notified If for example the remote computer is z OS system a WTO macro is issued by Unicenter CA
264. fies the unit name to be used in locating the local data set Value Definition Up to 10 alphanumeric Specifies the unit name to be used in locating the local characters data set If the data set does not exist and the File Allocation Information screen is used the parameters entered on that screen will be used to create the data set If the data set does not exist and the File Allocation Information screen is not used the file allocation parameter values specified in the Default Options Table is used to create the data set Notes This parameter is used in conjunction with the local Volume parameter Default Catalog information is used if the data set exists Extended Remote File Name Entry Screen The MVS Extended Remote File Name Entry screen is used to specify a Remote File Name longer than 65 characters A maximum of 256 characters is allowed It is accessed from the Send File or Receive File screens by entering a plus sign in the first position of the Remote File Name field and pressing ENTER Unicenter CA XCOM r11 5 00 TURKIO1 MVS Extended Remote File Name Entry Remote File Name Maximum 256 characters PFK 1 Help 3 End COMMANDS gt 1 1 F2 SPLIT F4 RETURN F5 RFIND 6 F7 UP F8 DOWN F9 SWAP FlO0 Language 11 1 F12 Alloc 2 98 User Guide Japanese Character Set Support Screen Japanese Character Set Support Screen The Japanese Character Set Support Screen is used to transf
265. for Stratus can use its own account file to verify the user ID and password and to map the Unicenter CA XCOM Data Transport user ID to a VOS user ID to check for file access If this option is turned on and the remote user ID password combination is invalid Unicenter CA XCOM Data Transport for Stratus rejects the request Restart Recovery facility Unicenter CA XCOM Data Transport for Stratus can attempt periodic data transmissions after the initial file transfer has failed A certain number of retries can be specified through the xcom ser pm file The following restrictions apply to Unicenter CA XCOM Data Transport for Stratus No checkpoint restart Unicenter CA XCOM Data Transport for Stratus Version 1 does not support checkpoint restart No library transfers Unicenter CA XCOM Data Transport for Stratus does not support the transfer of libraries from z OS Remote System Information 9 13 Tandem Tandem This section contains information about important aspects of the Tandem operating system Naming Conventions Example 9 14 User Guide Use the following format to name a Tandem file lt system lt volume subvolume filename of these components are restricted to eight characters except as indicated below The following table describes the parts of a Tandem file name Part Description system The system name Up to seven characters volume The disk name subvolume be thought
266. from the number of batch jobs still in the process of being executed The indicated ACBNAME must be a valid VTAM ACBNAME otherwise the transfer fails and error messages are written to the job log Only one file transfer using the APPLID can be active at a time All others wait until the APPLID becomes available no time out occurs in this case We recommend indicating a generic APPLID because it allows up to 1000 concurrent file transfers Leaving this parameter unspecified allows the value of the JOBACB parameter in the Unicenter CA XCOM Data Transport Default Options Table to govern The Batch Interface 3 9 PARM Parameters COMPNEG 3 10 User Guide Specifies whether compression negotiation is performed Value Definition YES Specifies that the data compression method is negotiated NO Specifies that the data compression method is not negotiated Notes If COMPNEG YES and the compression method suggested by the initiator or partner LU is known to both participants that method is used to compress the transfer data If the suggested compression method is not known to a participant involved in the transfer Run Length Encoding of blanks and zeros that is COMPRESS YES see the next section is applied to the data to be transferred Also z OS initiated transfers to a partner defined in the XCOMCNTL destination member as a version 1 node use COMPRESS YES if an unsupported compression method COMPACT COMPACTL RLE HUFFMAN ZLI
267. g non cataloged files This value can be up to 10 alphanumeric characters Notes If a data set does not exist and the File Allocation Information screen is used the parameters of this screen will be used If a data set does not exist and the File Allocation Information screen is not used system wide defaults specified in the Unicenter CA XCOM Data Transport Default Options Table will be used Default Catalog information is used Indicates the unit name on the remote system on which the file is to be created or resides for existing non cataloged files Value Definition XXXXXXXX Specifies the unit name on the remote system on which the file is to be created or resides for existing non cataloged files This value can be up to eight alphanumeric characters Notes If a data set does not exist and the File Allocation Information screen is used the parameters of this screen is used If a data set does not exist and the File Allocation Information screen is not used system wide defaults specified in the Unicenter CA XCOM Data Transport Default Options Table is used Default Catalog information is used Send MVS File To Another System Screen Local System Information User ID The Local System Information fields of the Send MVS File To Another System screen pertain to the local or transfer initiating Unicenter CA XCOM Data Transport system Identifies the user ID under whose set of resource access privileges this fi
268. gical units that has been previously defined in the Unicenter CA XCOM Data Transport Destination Table or to a single TCP IP partner Value Definition XXXXXXXX Specifies up to eight alphanumeric or national characters representing a group of previously defined logical units where the first available LU should receive this file transfer The initial character must be national or alphabetic The XCOM group name can also be used to provide an alias for a single LU IP name or IP address Notes This parameter is mutually exclusive with SNA LU Name Login User Name IP Name and XCOM List Name one of the five must be specified for each file transfer request XCOM List Name Login User Name The Primary Option Menu Used when this file transfer is to be broadcast to all the remote destinations designated on a predefined distribution list Value Definition xxxxxxxx Enter up to eight alphanumeric characters representing the name of a list to which this transfer is to broadcast Notes This parameter is mutually exclusive with XCOM Group Name Login User Name SNA LU Name and IP Name one of the five must be specified for each file transfer request This parameter is valid only for queued transfers As a result some of the file transfers may start at different times The Menu Interface s Transfer Request Display screen can be used to check the current completion status of the file transfers initiated by a broadcast distribution
269. gt lt X gt lt gt x x gt lt gt x gt x gt gt lt gt lt X gt x x x gt lt gt x gt x gt gt lt gt lt gt lt gt x gt x gt x gt lt gt x gt x gt gt x X gt lt gt x gt x x x gt x gt x gt x gt lt gt lt X X gt x gt x x gt x gt x gt gt lt gt lt gt x gt x gt x gt x 00 517 5 8585 5 00 55 00 5 07 Sample XCOMDFLT Macro Member XCOMDFLT RUSIZE SEC PRI 256 PRIMARY SEND SECONDARY SEND PACING COUNT PACING COUNT SECONDARY RECEIVE PACING COUNT gt lt gt x gt x gt x gt x PSERVIC X 060200000000000000000300 PRESENTATION SRVCS MODEEND END Sample XCOMDFLT Macro Member XCOMDFLT The following is a copy of the sample XCOMDFLT Macro CAI CINBOSAM XCOMDFLT found on the distribution tape The table contains a sample of the parameters in the Default Options Table XC000010 KKK K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K XC000020 CA XCOM FOR MVS DEFAULT OPTIONS TABLE 1 MAKE SURE ALL CONTINUATION LINES START AT COL 16 2 REFER TO MANUAL FOR DETAILS OF PARAMETER MEANING XC000030 XC000040 XC000050 KKK K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K K 000060 DFLTAB ACBNAME XCOMAPPL
270. han one causes an error When GROUP or LIST is used the value for IPPORT is determined by either the destination member or the default table When a transfer is performed to a destination defined as a list of LUs or IP addresses the data is transferred to each LU or IP node in the list The LU and IPNAME parameters can be coded within the same list member This results in the file being transferred to SNA and IP nodes The LIST parameter is valid only for TYPE SCHEDULE transfers Since a transfer to a list destination is processed as a queued request the various file transfers involved might have different start times Use the Unicenter CA XCOM Data Transport Operator Control function on the Menu Interface to check the current status of any broadcast distribution Indicates a password associated with LUSER This is mainly used for third party initiated file transfer requests Value Definition xxxxxxxx Specifies a password of up to eight alphanumeric characters that is associated with LUSER Notes LPASS should not be confused with PASSWORD see below The Batch Interface 3 43 SYSINO1 Parameters LU LUSER 3 44 User Guide Defines the LU name of the remote system LU identifies the VTAM logical unit name associated with the remote computer Value Definition xxxxxxxx Specifies the name of the remote LU The name may contain up to eight alphanumeric characters Notes GROUP LIST USER LU and IPNAME are mutu
271. he transfer completes the message is displayed next time the user does log on LOG LOG requests that the main operator on the remote computer be notified If for example the remote computer is z OS system a WTO macro is issued by Unicenter CA XCOM Data Transport On an AS 400 or VAX system the operator console is notified Default LOG Send Report To Another System Screen Local System Information User ID The following parameters are accessed under Local System Information Identifies the user ID under whose set of resource access privileges this file transfer is to execute on the source computer Value Definition Up to eight Specifies the user ID whose privileges are used for executing alphanumeric this file transfer on the source computer characters Notes This information is primarily used for third party processing For example a Unicenter CA XCOM Data Transport node in New York could request that a Unicenter CA XCOM Data Transport node in Los Angeles send a file to a Unicenter CA XCOM Data Transport node in Chicago To use this feature all systems must be identified to VTAM and running Unicenter CA XCOM Data Transport Version 2 or higher For conventional non third party file transfers use this parameter to identify the user that initiated the transfer This is useful when performing operator tracking and control functions through the Unicenter CA XCOM Data Transport Operator Control screen To send a bl
272. he transfer requests to be purged when the current file transfer completes successfully Value Definition Up to 8 transfer Specifies up to eight jobs to be purged if a transfer request names completes successfully Specifies the transfer requests to be released if the current file transfer concludes successfully Value Definition Up to 8 transfer Specifies up to eight jobs to be released if a transfer request names completes successfully Defines the name of a transfer request belonging to the group of interdependent transfer requests named through the XTCNET parameter Value Definition xxxxxxxx Specifies the name of a transfer request in a group of interrelated transfer requests Default z OS job name of the z OS job requesting the file transfer The Batch Interface 3 77 SYSINO1 Parameters XTCNET Defines the name of a group of interdependent transfer requests Value Definition xxxxxxxx Specifies up to eight alphanumeric characters representing the name of the XTC network running this transfer Note When using the XCOMPLEX all transfers with the same XTCNET value are distributed to the same XCOMPLEX Worker Server 3 78 User Guide Coding Interdependent Transfers SYSINO1 Parameters This section explains how to code a set of interdependent transfers in the SYSINO1 DD statement m The SYSINO1 parameter NEWXFER must be used at the beginning of each of the multiple transfer requests as shown in the following d
273. hether a given user ID or console is authorized to issue Unicenter CA XCOM Data Transport commands The commands whose access status is verified include z OS console commands and commands that can be issued through ISPF and CICS menu interfaces Pariner Security Unicenter CA XCOM Data Transport makes standard SAF calls to determine whether a given user ID is authorized to perform transfers with a given partner Additionally Unicenter CA XCOM Data Transport checks whether the direction send receive in which the transfers are performed is authorized and whether the partner making a transfer request can be the initiator of transfers Overview of Unicenter Data Transport Security 8 1 Invoking Security Invoking Security Each security function can be turned on separately via the assembled Default Options Table in the Unicenter CA XCOM Data Transport load library Also each security function has an associated user exit which increases the flexibility of Unicenter CA XCOM Data Transport s security and allows security to be adapted to site specific conditions For more detailed information see the chapter Security Considerations in the Unicenter CA XCOM Data Transport for z OS Administrator Guide Data Encryption Using Secure Socket Layer SSL 8 2 User Guide Unicenter CA XCOM Data Transport uses OpenSSL to utilize the Secure Socket Layer SSL to perform secure TCP IP transfers between platforms running Unicenter
274. iagram L JOBNAME STEP1 PGM XCOM PARM parm parm value SYSINO1 DD transfer request 1 parameters NEWXFER XCOMJOB JCL SYSINO1 transfer request 2 parameters NEWXFER transfer request 7 parameters The NEWXFER parameter is used in the SYSINO1 DD statement to signal the beginning of each new transfer request 1 2 1 The Batch Interface 3 79 SYSINO1 Parameters 3 80 User Guide m The parameter XTCNET is used to indicate which transfer requests belong to the same group are dependent on each other Suppose for example that the transfers XFER1 XFER2 and XFER3 need to be grouped together This can be accomplished simply by assigning the name of the group say GROUP1 to XTCNET and including XTCNET GROUPI in the definition of each of the three transfer requests If XTC transfers are requested using the XCOMPLEX the XCOMPLEX Admin Server distributes all transfers with the same value for to the same XCOMPLEX Worker Server m Each interdependent transfer request must have a unique name which is assigned to the XTCJOB parameter Thus if XFER1 XFER2 and are the names of three interdependent transfer requests their definitions in SYSINO1 must contain the parameter XTCJOB XFER1 XTCJOB XFER2 and XTCJOB XFER3 respectively
275. icenter CA XCOM Data Transport Default Options Table or in the EXEC statement of the Unicenter CA XCOM Data Transport start up JCL The ENABLE command can optionally be used by the XCOMPLEX Admin Server For more information see Enable and Disable Commands in the Unicenter CA XCOM Data Transport for z OS Administrator Guide Command Security Requirements 6 24 User Guide The use of the command requires that the security authorization for the command issuer contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec ENABLE membername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m membername the name of the control library member to be enabled EXIT Command Format Operands Notes Using the Unicenter CA XCOM Data Transport MODIFY Commands Executes a user written Unicenter CA XCOM Data Transport exit routine F XCOM EXIT userdata The following operand is used with the EXIT command Operand Description userdata Specifies up to eight bytes of data to be passed to the XCOMEX09 routine The use of the command requires that the security authorization for the command issuer contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name READ XCOM applsec EXIT data The variables represent the following values m applse
276. icenter CA XCOM Data Transport s control library and then enable the member again DISABLE can optionally be used by the XCOMPLEX Admin Server For more information see ENABLE and DISABLE Commands in the chapter Configuring and Customizing Unicenter CA XCOM Data Transport in the Unicenter CA XCOM Data Transport for z OS Administrator Guide Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Resource Name Level UPDATE XCOM applsec DISABLE membername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m membername the name of the CONTROL LIBRARY member to be disabled Operation and Control 6 19 Using the Unicenter CA XCOM Data Transport MODIFY Commands DISPLAY Command Displays information about active sessions Format F XCOM DISplay destname Operands The following operand is used with the DISPLAY command Operand Description destname The name of the destination about which session information is to be displayed The destination can be identified with 1 a valid SNA LU name 2 TCP IP name or 3 TCP IP address For information about all active sessions running under this started task omit this operand Notes The DISPLAY command lists established sessions involving the local computer even
277. ide Describes the contents of the report being sent to the remote system Value Definition Up to 21 Text describing the contents of the report being sent to the alphanumeric remote system characters Notes Depending on the operating system running on the remote system this parameter might only be used as a comment or it might become part of the banner page produced with the report For example Digital Equipment Corp VAX VMS systems will print this field in a banner page On a z OS system this entry becomes part of the banner page with the values specified in the Print Class and Form Type parameters Indicates the number of report copies to be printed on the remote system Value Definition 1 to 256 Specifies the number of report copies to be printed on the remote system Default 1 Value Definition Up to 12 Specifies the type of form that is used for printing on the alphanumeric remote system characters Record Separators EBCDIC Binary ASCII Truncate Record Send Report To Another System Screen Specifies whether Unicenter CA XCOM Data Transport adds a record separator to delimit logical records Note Skip this field unless you are sending data to an ASCII computer Value Y N Default N Definition Unicenter CA XCOM Data Transport adds a record separator such as a line feed and carriage return to delimit logical records Unicenter CA XCOM Data Transport does not add record separators I
278. ies the length in days of the queue purging interval applied to locally initiated transfer requests CATALOG Indicates whether new data sets created by Unicenter CA XCOM Data Transport should be cataloged CLASS Specifies the default SYSOUT class assigned to an incoming report when the remote system does not provide one DIR Specifies the number of PDS directory blocks to be allocated for file transfers to new data sets DUMPCL Specifies the SYSOUT class Unicenter CA XCOM Data Transport uses when creating diagnostic dumps EDESC Specifies the sixteen bits coded in hexadecimal of an MVS message descriptor code EROUT Specifies the sixteen bits coded in hexadecimal of MVS console routing codes for error messages ending with E ERRINTV The interval in minutes at which Unicenter CA XCOM Data Transport is to reset error flags on the pending request queue and retry session establishment IDESC Specifies the sixteen bits coded in hexadecimal of an MVS message descriptor code IROUT Specifies the sixteen bits coded in hexadecimal of an MVS console routing code 6 16 User Guide Using the Unicenter CA XCOM Data Transport MODIFY Commands Operand Description JESINTV Sets the interval in seconds at which the Unicenter CA XCOM Data Transport server is to scan the JES spool for output directed to destinations and or writers specified in CAI CIN31CTL destination me
279. if currently idle It also displays the name of the associated partner logical unit whether it is currently sending or receiving and the number of records transferred so far If this computer is serving as the intermediary system in an active indirect file transfer this session is also displayed Repeating the DISPLAY command several times and tracking the record count allows you to check whether a transfer is proceeding normally 6 20 User Guide Using the Unicenter CA XCOM Data Transport MODIFY Commands Command Security Requirements DUMP Command Format Operands The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name READ XCOM applsec DISPLAY destname XCOM applsec DISPLAY The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination about which session information is to be displayed m asterisk any or all sessions Dumps control blocks for a Unicenter CA XCOM Data Transport partner F XCOM DUMP des tname The following operand is used for the DUMP command Operand Description destname Specifies the destination in which you are interested The destination can be identified with 1 an SNA LU name 2 name or 3 TCP IP address The Unicenter CA XCOM D
280. ifies that the records to be packed into fixed size data transfer blocks Each record begins with a 2 byte long prefix that indicates the length of the record and determines how many records can be packed into a block The default block size is 2K but it can be increased to 31K by using the MAXPACK parameter in the Unicenter CA XCOM Data Transport Default Options Table or in the Unicenter CA XCOM Data Transport control library member When transferring a text file to a partner that supports record separators for example CRLF OD0A on Windows 2000 2003 or XP and LF 0A on UNIX record separators will be inserted No separators are inserted in binary files transferred with PACK LENGTH CRLF Specifies that the records are to be packed into blocks separated by a C arriage R eturn L ine F eed byte sequence Notes PACK LENGTH with MAXPACK 31744 should be selected when using Unicenter CA XCOM Data Transport over TCP IP If PACK LENGTH is coded then you must also code RECSEP NO Platforms that understand PACK LENGTH are IBM s AS 400 UNIX based systems and z OS systems See the appropriate documentation for the platform to see if this value is supported CRLF packing can be used with text files only It is also used when communicating with older releases of Unicenter CA XCOM Data Transport on PC DOS and OS 2 The Menu Interface TSO ISPF Panels 2 59 Send Report To Another System Screen Transfer User Data System Use
281. ify up to 10 bytes of any type of data to be associated with the transfer request The user data is sent to all user exits and written to the history file upon completion of the file transfer Value Definition Up to 10 alphanumeric Specifies data to be associated with the transfer characters request System User Data Receive File From Another System Screen Allows the specification of transfer dependent user data This data is available to user exits in the RRDSUSER field of the RRDS data area mapped by the RRDDSECT macro while the transfer is pending or active The RRDSUSER field is defined by HDRDSECT within RRDDSECT Value Definition 1 to 10 bytes Specifies up to 10 bytes of data available to user exits during a file transfer Remote System Information User ID The Remote System Information fields of the Receive File From Another System screen pertain to the remote or non initiating Unicenter CA XCOM Data Transport partner Identifies the user ID under whose set of resource access privileges the file transfer is to execute on the remote system It should be a user ID known to the security interface of that system Value Definition XXXXXXXXXXXX Specifies up to 12 alphanumeric characters representing a user ID whose access privileges on the remote system are used for executing the transfer Notes If the remote system does not perform security checking you can skip this and the Remote Password parameter To send
282. indows and so on while z OS menus are written for the popular ISPF Dialog Manager Batch Command Line Interface Unicenter CA XCOM Data Transport can also be initiated with a batch file on your computer For example a transfer can be invoked through a JCL batch job on z OS and a CMS EXEC on VM On mini and microcomputers a transfer can be initiated via a command entered at the operating system prompt command line or placed in a batch file to be executed with other commands Introduction 1 1 Invoking Unicenter CA XCOM Data Transport Programming Interface 1 2 User Guide Any programming language supporting callable subroutines can call Unicenter CA XCOM Data Transport Examples of calling programs from common programming languages are given in each user manual for supported platforms For instance the OS 2 and PC DOS versions of Unicenter CA XCOM Data Transport allow direct API calls to specific Unicenter CA XCOM Data Transport functions in addition to allowing you to run Unicenter CA XCOM Data Transport as a subprogram Unicenter CA XCOM Data Transport also provides exits on many systems that allow you to control or be informed about certain Unicenter CA XCOM Data Transport events involving security and completed transfers Unicenter CA XCOM Data Transport Connectivity Unicenter CA XCOM Data Transport Connectivity The following diagram shows how Unicenter CA XCOM Data Transport can provide connectivity across very diverse enviro
283. ined The Batch Interface 3 73 SYSINO1 Parameters Examples of DCB Information The following are examples of DCB information that you can code in your SYSINO1 data set depending on the type of files being created Example 1 RECFM FB LRECL 80 BLKSIZE 8000 Example 2 RECFM VB LRECL 516 BLKSIZE 23440 Example 3 RECFM U BLKSIZE 19069 SYSINO1 Transfer Control XTC Parameters The SYSINO1 parameters described in this section form a feature of Unicenter CA XCOM Data Transport known as Unicenter CA XCOM Data Transport Transfer Control XTC These parameters are used to handle dependencies between multiple transfers For example one transfer must complete in a certain way before another can start They provide the means by which interdependent transfer requests can be defined and processed as a single group A transfer request belonging to sucha group can cause another transfer request in the same group to be held purged or released either conditionally or unconditionally from the transfer request queue For further discussion of interdependent transfers see the section Coding Interdependent Transfers that follows the list of XTC parameters Delimiting Multiple Parameter Values 3 74 User Guide Several XTC parameters can be assigned up to eight values typically transfer request names at the same time When assigning multiple values to a parameter commas must be used to separate the parameter values XTC_PARAME
284. ines a PDSE PDS Defines a partitioned data set lt blank gt Defines a partitioned or sequential data set based on the data set characteristics entered Note These values are IBM standards for SMS processing Default None The Batch Interface 3 35 SYSINO1 Parameters EPRTY Indicates the execution priority for the request The lowest priority is 1 Value Definition 1 to 255 Specifies an execution priority from 1 to 255 where 1 is the lowest priority Notes In an environment with multiple concurrent Unicenter CA XCOM Data Transport transmissions transfers with higher priorities receive preferential servicing other considerations being equal give short file transfers a higher EPRTY than very long running transmissions Default 16 FILETYPE Indicates the output type of the transfer on the target computer Required Value Definition FILE Indicates that the transferred information is a file to be stored on the external media of the receiving system This parameter value can be used with TYPE SEND and TYPE RECEIVE requests JOB Indicates that the transferred information is a batch job submitted for execution on the remote computer This parameter value can be used only with TYPE SEND requests REPORT Indicates that the transferred information is a report to be printed on the remote computer This parameter value can be used only with TYPE SEND requests 3 36 User Guide GROUP SYSINO1 Parame
285. ing this exit CAI CINBOSAM XCOMEX86 This exit point allows execution of a user developed exit routine that validates user supplied Unicenter CA XCOM Data Transport transfer parameters The exit is called after all standard Unicenter CA XCOM Data Transport validation has been performed and the Unicenter CA XCOM Data Transport transfer request control block that is mapped by the RRDDSECT macro found in CALCINBOMAC has been built The routine may tell Unicenter CA XCOM Data Transport to accept or reject the request by setting a flag in the exit parameter list The exit routine may also provide an installation defined error message via the same parameter list Module Name and Eniry Point How to Enable Calling Module Entry Method Required DSEC The module name and entry point for this exit is XCOMEXO07 Specify 07 in the Default Options Table to enable this exit The module XCOMEXIT calls this exit This exit is a branch entry EX07PLST is the required DSECT Addressing Mode at Entry The addressing mode at entry is 31 User Exits 0 15 User Exit 7 Registers at Entry Registers at Exit Valid Return Code Sample Program D 16 User Guide The following registers are available at entry Register Description RO Undefined R1 Address of EXO7PLST R2 to R12 Undefined R13 Address of register save area R14 Return address R15 Entry point address The following registers are available at ex
286. int data when an interrupted transfer is restarted The same global data set should be used for all TYPE EXECUTE job streams that run under the same ACBNAME Records the request numbers for TYPE SCHEDULE transfers Records the restart information for TYPE EXECUTE file transfers If a file transfer fails due to a restartable condition such as a line failure the XCOMREST file holds the information needed to restart the file transfer request from the last checkpoint If you do not enter the XCOMREST DD statement in the JCL the restart of a TYPE EXECUTE request is not supported by Unicenter CA XCOM Data Transport The Batch Interface 3 7 XCOMJOB Parameter Classes The XCOMREST DD statement should not be used with TYPE EXECUTE transfers that have specified CONTINUE YES in the PARM statement with one or more NEWXFER statements in the SYSINO1 data set Such requests cannot be restarted in a reliable manner This data set should be a single 1100 byte one record sequential file and must not be a member of a PDS A unique XCOMREST data set is required for each transfer XCOMJOB Parameter Classes 3 8 User Guide The batch interface for Unicenter CA XCOM Data Transport makes available a large number of transfer control parameters They are divided into two classes based on where they can be used in the XCOMJOB JCL One set of parameters can be specified only in the PARM field of the EXEC statement and the other can be specified only in th
287. interface sample COBOL program 4 3 APPLID Selection menu 2 10 VTAM APPLID definition table C 10 APPLXCOM sample JCL C 10 AS 400 9 2 2 sample JCL C 33 ASMRACFU sample JCL C 30 ASMTOPSU sample JCL C 31 ASSEMBLER program calling Unicenter CA XCOM Data Transport from 4 5 attribute labels 2 116 banner page user exit D 21 batch job parameters See PARM parameters and SYSINO1 parameters batch multiple transfers 3 2 3 45 BLKSIZE SYSINO1 parameter 3 72 broadcast distributions 3 2 bytes Detailed File Transfer screen 2 121 bytes sec Detailed File Transfer screen 2 121 C CANCEL MODIFY command 6 11 CANCLD status field 2 118 CATALOG system parameter 6 16 CHARS SYSINO1 parameter 3 62 checkpoint count Receive File From Another System screen 2 88 CICS COPYCSD C 37 define CICS default file sample JCL C 35 define Help File sample JCL C 34 direct spool interface 5 6 sample notification transaction C 23 transactions 5 2 XCOMECT sample JCL C 38 XCOMPCT sample JCL C 39 Index 1 XCOMPPT sample JCL C 40 XCOMTCT sample JCL C 41 CKPT SYSINO1 parameter 3 31 CLASS SYSINO1 parameter 3 62 system parameter 6 16 CLIST library 2 2 CNOS MODIFY command 6 13 COBOL calling Unicenter CA XCOM Data Transport from 4 3 CICS sample C 23 Code Table parameter 2 25 2 56 2 73 2 90 CODE SYSINO1 parameter 3 32 CODETABL PARM parameter 3 30 coding interdependen
288. ion Y Specifies that records larger than the maximum LRECL are to be truncated to the maximum record length N Specifies that Unicenter CA XCOM Data Transport is to terminate the file transfer upon receiving a record larger than the maximum LRECL Notes This field is supported only by the Unicenter CA XCOM Data Transport mainframe products Unicenter CA XCOM Data Transport for z OS Unicenter CA XCOM Data Transport for VSE and Unicenter CA XCOM Data Transport for VM When a record is truncated the data not within the LRECL limit is lost Default N This is a 3 character alphanumeric field used for specifying the translation table to be used by the remote partner for this particular transfer only This field is applicable only for transfers to Unicenter CA XCOM UNIX or Windows 2000 2003 or XP partners and only if their INTERNAL CONVERSION TABLES NO Value Definition 1 to 3 bytes Specifies up to alphanumeric characters identifying the code table to be used by the remote partner Secure Socket SSL Checkpoint Count Send MVS File To Another System Screen Informs Unicenter CA XCOM Data Transport how to handle the security of the transfer to the remote system Value Definition YES Tells Unicenter CA XCOM Data Transport to use OpenSSL for the transfer of the file and that it must connect to a SSL port on the remote partner NO Tells Unicenter CA XCOM Data Transport that the file does not require a secure
289. is automatically displayed if a non existent file is specified in the Local File Name field of the Receive File From Another System screen It can also be invoked by pressing the PF12 key on the Receive File From Another System screen If the remote system is a z OS computer and the file specified in the Remote File Name field on the Send MVS File to Another System screen does not exist press the PF12 key to invoke the File Allocation Information Screen If the Remote File Name field is blank the name in the Local File Name field will be used as the Remote File Name When the File Allocation Information screen is called from the Send MVS File To Another System screen any allocation parameters set on it describe the file to be created on the remote system the target of the send operation When the File Allocation Information screen is called from the Receive File From Another System screen any allocation parameters set on it describe the file to be created on the system initiating the receive operation The Menu Interface TSO ISPF Panels 2 41 File Allocation Information Screen Parameter Defaults The defaults for the allocation parameters have three different sources m If the data set already exists on the local system and the File Allocation Information screen is or is not used the defaults come from catalog information m If the data set does not exist on the local system and the File Allocation Information screen is used the
290. it Register Description RO to R14 Undefined R15 Return code The only valid return code is 0 for a normal return Note The return code from the exit is passed in field EXO7RC of the exit parameter list which is mapped by the EX07PLST macro found in CAI CINBOMAC The following is a sample program using this exit CAI CINBOSAM 7 User Exit 8 Purpose User Exit 8 This exit point allows execution of a user developed exit routine that performs user defined initialization and termination processing for the Unicenter CA XCOM Data Transport server This exit allows extension of Unicenter CA XCOM Data Transport with user supplied control blocks and processing For example the exit can acquire GETMAIN and release FREEMAIN control blocks or load custom user modules Module Name and Entry Point How to Enable Calling Module Entry Method Required DSECT The module name and entry point for this exit is XCOMEX08 Specify 08 in the Default Options Table to enable this exit The module XCOMXFER calls this exit This exit is a branch entry EXO8PLST is the required DSECT Addressing Mode at Entry The addressing mode at entry is 31 User Exits D 17 User Exit 8 Registers at Entry Registers at Exit Valid Return Code Sample Program D 18 User Guide The following registers are available at entry Register Description RO Undefined R1 Address of EXOSPLST R2 to R1
291. it 5 Purpose This exit point allows execution of a user developed exit routine that provides additional security checking before a transfer takes place The exit is used with the system security option chosen in the Unicenter CA XCOM Data Transport Default Options Table s SECURITY parameter for example IBM RACF eTrust CA Top Secret Security or eTrust 2 Security Module Name and Entry Point How to Enable Required DSECT The module name and entry point for this exit is XCOMEX05 The exit is entered for TYPE EXECUTE and TYPE SCHEDULE transfers The exit is entered after session establishment Specify 05 in the Default Options Table to enable this exit SECDSECT is the required DSECT Calling Module and Entry Sequence D 10 User Guide This exit is called by the module XCOMFILE which in turn is called either by or XCOMXFER For SNA transfers the SECLUN field of SECDSECT contains the target LU for TYPE EXECUTE XCOMJOB transfers and TYPE SCHEDULE transfers queued to the Unicenter CA XCOM Data Transport for z OS started task For IP transfers the SECLUN field of the SECDSECT contains the hexadecimal representation of the partner s IP address if TCPLUSEC binary is specified in the Unicenter CA XCOM Data Transport default options table The exit is also entered when XCOMJOB is executed with TYPE SCHEDULE In this case SECLUN contains the APPLID of the Unicenter CA XC
292. ith a 2 byte long prefix that indicates the length of the record and determines how many records can be packed into a block The default block size is 2K but it can be increased to 31K by using the MAXPACK parameter in the Unicenter CA XCOM Data Transport Default Options Table or in the Unicenter CA XCOM Data Transport control library member When transferring a text file to a partner that supports record separators for example CRLF OD0A on Windows 2000 2003 or XP and LF 0A on UNIX record separators will be inserted No separators are inserted in binary files transferred with PACK LENGTH CRLF Specifies that the records are to be packed into blocks separated by a C arriage R eturn L ine F eed byte sequence Notes PACK LENGTH with MAXPACK 31744 should be selected when using Unicenter CA XCOM Data Transport over TCP IP If PACK LENGTH is coded then you must also code RECSEP NO Platforms that understand PACK LENGTH are IBM s AS 400 UNIX based systems and z OS systems See the appropriate documentation for the platform to see if this value is supported CRLF packing can be used with text files only It is also used when communicating with older releases of Unicenter CA XCOM Data Transport on PC DOS and OS 2 The Menu Interface TSO ISPF Panels 2 29 Send MVS File To Another System Screen Transfer User Data System User Data 2 30 User Guide Allows the user to specify up to 10 bytes of any type of data to be ass
293. ities receive preferential service In a busy Unicenter CA XCOM Data Transport environment unless you have compelling reasons for not doing so enhance processing efficiency by giving short file transfers a higher priority value than long running transmissions Default 16 Local File Name File Sequence Send Report To Another System Screen Indicates the name of the local data set being transferred Required Value Definition Up to 56 Specifies up to 56 characters consisting of the following alphanumeric characters m 1 1 44 character data set name m An optional member name enclosed in parentheses m Optional single quotation marks apostrophes to enclose the data set The user s TSO profile prefix is inserted at the beginning of this entry unless the entry is enclosed in single apostrophes If the TSO profile is set to NOPREFIX nothing is inserted Use an asterisk to send multiple members of a partitioned data set Specifying an asterisk for the member name will send all members of a PDS for example SURVEYS To send all members beginning with a specific prefix specify this prefix followed by an asterisk For example NAMES PDS AL requests that members AL ALEX and ALICE all be transferred The asterisk must be the last character before the right parentheses If no member name is entered for a partitioned data set a Member Selection List panel will be displayed allowing the selection of one or more members for t
294. its LUD1 LUD2 and LUD3 and assigns them a group name of LAVAX Code the GROUP and LU parameters for this entry as follows GROUP LAVAX LU LUD1 LUD2 LUD3 Type LAVAX as the remote system name to schedule transmissions to this VAX through the menu interface When using the batch interface use the GROUP parameter instead of the LU parameter Use the following code GROUP LAVAX Groups can be used with all the Unicenter CA XCOM Data Transport interfaces including the Process SYSOUT Interface Initiating the session bind request Although separate VTAM LU names can be used for Unicenter CA XCOM Data Transport sessions you should not LOGAPPL these LUs to Unicenter CA XCOM Data Transport when configuring on z OS or VM This will fail with an 0801 or 8003 sense code since the DEC software must initiate the session bind request Remote System Information 9 9 OS 2 OS 2 Compression options Pack options are not supported Only COMPRESS YES is supported for compression for versions prior to version 3 0 m ASCII based The OpenVMS platform is ASCII based system This section contains information about important aspects of the OS 2 operating system Naming Conventions 9 10 User Guide OS 2 supports the FAT file system and the High Performance File System HPFS This section addresses the HPFS format Use the following format to name an OS 2 file in the HPFS format d N directory name N
295. k next to the displayed value of DROPSESS GETSESS LOGMODE LOGNREO or VERL indicates that the value is taken from the Default Options Table The LIST command cannot be used for Custom Code Page Conversion Tables TYPE CONVERT Command Security Requirements 6 28 User Guide The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name READ applsec LIST membername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m membername the name of the control library member Using the Unicenter CA XCOM Data Transport MODIFY Commands LOGFREE Command Format Notes Frees the Unicenter CA XCOM Data Transport log for printing F XCOM LOGFREE This commands closes and de allocates the current logging data set then dynamically allocates and opens the new logging data set It allows you to review the contents of the Unicenter CA XCOM Data Transport log while Unicenter CA XCOM Data Transport is active Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec LOGFREE The applsec variable represents the value of the APPLSEC paramete
296. ke Unicenter CA XCOM Data Transport that communicate with other transaction programs using LUs In a Unicenter CA XCOM Data Transport transfer request the local end user specifies the following m of transfer send report file or job or receive file m Name of the local file Name of the remote file to create append or replace The request is then processed by the Unicenter CA XCOM Data Transport transaction program on the local system that sends an allocate verb and header record to the remote system to establish an LU 6 2 session When a session is established and all of the parameters are confirmed by the remote system Unicenter CA XCOM Data Transport on the local system will send the file broken into data records across the physical connection The remote Unicenter CA XCOM Data Transport transaction program is then invoked by the allocate verb sent by the local system though some systems cannot be automatically invoked and must already be active to receive the allocate verb The remote transaction program then creates or opens the requested file receives the data records and places them in the file When all the records have been received Unicenter CA XCOM Data Transport on the remote system will send a trailer record to the local system stating the number of records transmitted User Guide 1 4 The Logical Level The Physical Level Network Levels in the SNA Model The logical level consists of logical uni
297. le transfer is to execute on the source computer Value Definition XXXXXXXX Specifies up to 8 characters representing the user ID under whose set of resource access privileges this file transfer is to execute on the source computer Notes This parameter is ignored by the local security software system For conventional that is non third party file transfers this parameter is used to identify the user that initiated the transfer This is useful when performing operator tracking and control functions through the Unicenter CA XCOM Data Transport Operator Control screens The primary use of this parameter is for third party processing For example a Unicenter CA XCOM Data Transport node in New York can request that a Unicenter CA XCOM Data Transport node in Los Angeles send a file to a Unicenter CA XCOM Data Transport node in Chicago Default TSO user ID The Menu Interface TSO ISPF Panels 2 35 Send MVS File To Another System Screen Tape Password 2 36 User Guide Indicates whether the local data set resides on magnetic tape Value Definition Y Specifies that the local data set resides on magnetic tape N Specifies that the local data set does not reside on magnetic tape Notes If you enter Y in the Tape field a new screen MVS Extended Tape Parameter Entry see next section is displayed allowing tape related information to be specified Default N Specifies the password associated with the local User I
298. leted Q Indicates that the session is to be terminated if there are no additional transfer requests for the current Unicenter CA XCOM Data Transport partner Default N Remote File Name Send MVS File To Another System Screen Indicates the name of the file on the remote system receiving the data being transferred Required Value Definition Up to 256 Specifies the file name that should receive the data being alphanumeric transferred characters Notes When a Member Selection List is requested by omitting the member name from the entry used in the Data set Name field the Remote File Name field is scanned for the existence of any of the following special characters ef 19 5 amp QN OT During the generation of a file transfer request Unicenter CA XCOM Data Transport successively replaces each asterisk in a Remote File Name with a name the user has selected from the Member Selection List When Unicenter CA XCOM Data Transport finds no other special character in a Remote File Name it appends the name within parentheses of each selected member to the Remote File Name The user can arrange for Unicenter CA XCOM Data Transport to avoid the latter procedure and treat such a file as sequential To do this the user must select the ALLOC function PF12 24 and set the Directory Blocks entry to zero In the VAX VMS environment brackets are used to indicate the directory in a complete file name specification However s
299. llowing operands are used with the RESET command Operand Description asterisk Resets all error flags for all transfer requests destname Specifies the name of the Unicenter CA XCOM Data Transport destination for which the error flag is to be reset The destination name can contain up to eight alphanumeric characters Any of the following items may be used asa destination name m SNALU name m TCP IP name m TCP IP address m Unicenter CA XCOM Data Transport control library member name error flags are automatically reset by Unicenter CA XCOM Data Transport at an interval set by the ERRINTV parameter in Unicenter CA XCOM Data Transport s Default Options Table The default error reset interval is seven minutes If a transfer fails with a retry able error and the conditions leading to the failure have been corrected you can have the transfer retried before the error reset interval expires by using the RESET command Prior to issuing the RESET command use the SHOW command to verify that the status is NET ERR or REM SUSP and to determine the correct value to use for the destination name Using the Unicenter CA XCOM Data Transport MODIFY Commands Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec RESET destname The variables repres
300. lt Current value Note For this operand to be valid PARSESS YES must be coded in the control library member Operation and Control 6 13 Using the Unicenter CA XCOM Data Transport MODIFY Commands Notes Unicenter CA XCOM Data Transport attempts to initiate the Change Number of Sessions CNOS conversation with the partner LU only if the control library member specified is enabled When WINNERS or LOSERS are specified the group is updated with the necessary parameters and Unicenter CA XCOM Data Transport attempts to initiate the CNOS conversation with the partner LU The CNOS command cannot be used with single session SNA LUs or with TCP IP destinations CNOS can optionally be used by the XCOMPLEX Admin Server to establish a connection with the XCOMPLEX Worker Server in instances where a manual CNOS is necessary For more information see the section Enable and Disable Commands in the Unicenter CA XCOM Data Transport for z OS Administrator Guide Command Security Requirements 6 14 User Guide The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Resource Level UPDATE XCOM applsec CNOS membername The parameters represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m membername the name of the control library member Using the Unicenter CA XCOM D
301. m because Windows NT requires a valid user ID and password as defined when setting up a user account under NT to log in to or connect to an NT server User IDs and passwords are case sensitive Unicenter CA XCOM Data Transport uses the underlying NT security system to log in to the server as the user defined in the XCOM USERID parameter The authority to logon locally is required because there is no facility in Unicenter CA XCOM Data Transport for Windows NT to allow for another domain to be specified When transfer is sent from another system such as z OS USERID and PASSWORD must be supplied The following methods model sending from an XCOM MVS system to a local Windows NT drive Methods of handling NT systems security from Unicenter CA XCOM Data Transport Employing some security all users employ the same user ID Set XCOM USERID and XCOM_PASSWORD to a valid NT user ID and password that has local logon authority in the xcom glb file on the NT side On the MVS side send a transfer with parameter USERID blank between two single quotes This uses the user ID and password from the xcom glb file Employing user level security users employ their own user ID and password Set USERID and PASSWORD to an INVALID NT user ID and password in the xcom glb file on the Windows NT side On the MVS side send a transfer with parameters USERID and PASSWORD with a valid NT user ID that has local logon authority
302. m XTC parameters other than XTCNET and XTCJOB are used to indicate the dependencies obtaining between the transfer requests The outcome of a transfer request may affect as many as 8 other transfer requests In addition to the XTC parameters other SYSINO1 parameters and some for instance the local file name or LFILE must be used when defining interdependent transfer requests a HOLD YES must be coded in each transfer request that is dependent on the successful unsuccessful completion of another transfer request However HOLD YES need not be coded if the holding releasing of the transfer request is controlled by the HOLDCOUNT parameter shown following The following sample definition contains three interdependent transfer requests SYSINO1 DD NEWXFER Transfer request 1 follows TYPE SEND ILE A B C FILE MY FILE1 TCNET METS TCJOB PAYROLL OLD YES EWXFER Transfer request 2 follows YPE RECEIVE ILEZYOUR FILE FILE MY FILE2 TCNET METS TCJOB PAYME HOLD YES NEWXFER Transfer request 3 follows TYPE SEND FILE PC FILE LFILE MY PC FILE1 XTCNET METS XTCJOB GETDATA XTCGOODREL PAYROLL XTCGOODPURGE PAYME XTCERRPURGE PAYROLL XTCERRREL PAYME gt lt gt lt 2 lt lt SYSINO1 Parameters In this example the three transfer requests are identified as GETDATA PAYME and PAYROLL and they belong to the group METS Of these GETDATA is the parent transfer req
303. main operator on the local computer be notified If the local computer is a z OS system a WTO macro is issued by Unicenter CA XCOM Data Transport On an AS 400 or a VAX system the operator console is notified User_id If any value but LOG is given Unicenter CA XCOM Data Transport interprets this as a specific user ID on the local system If that user is not logged on when the transfer completes the message is displayed the next time the user logs on Default LOG Specifies the name of the volume serial where the local data set may be found or created Value Definition Up to six Specifies up to six alphanumeric characters representing the alphanumeric of the volume serial where the local data set may be characters found or created Notes Used in conjunction with the local Unit parameter The value must be the name of a volume currently mounted on this system or problems in allocation may occur If the data set does not exist and the File Allocation Information screen is used the parameters entered on that screen will be used to create the data set If the data set does not exist and the File Allocation Information screen is not used the file allocation parameter values specified in the Default Options Table will be used to create the data set Default Catalog information will be used if the data set exists The Menu Interface TSO ISPF Panels 2 97 Extended Remote File Name Entry Screen Unit Speci
304. mand issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Resource Level UPDATE XCOM applsec CANCEL destname type The parameters represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination Unicenter CA XCOM Data Transport partner involved in the transfer m type one of the CANCEL command Operands that is IMMED PURGE or SUSPEND CNOS Command Format Operands Using the Unicenter CA XCOM Data Transport MODIFY Commands Starts an SNA parallel session with the specified LU F XCOM CNOS yembername WINNERS27z0 LOSERS nnn The following operands are used with the CNOS command Operand Description membername Specifies the name of the control library member containing the definition of the partner LU The member name can be up to 8 alphanumeric characters long nnn Specifies a number in the range 0 to 999 which indicates either the number of contention winner or loser sessions depending on the associated operand see WINNERS and LOSERS in this table WINNERS Specifies the number nnn of contention winner sessions for an LU mode pair Default Current value Note For this operand to be valid PARSESS YES must be coded in the control library member LOSERS Specifies the number nnn of contention loser sessions for an LU mode pair Defau
305. mbers LOG Specifies whether the transfer log should be written LOGCL Indicates the JES SYSOUT class for the Unicenter CA XCOM Data Transport transfer log LOGDEST Specifies the JES destination for the Unicenter CA XCOM Data Transport transfer log Indicates the maximum number of locally initiated transfers MAXREM Indicates the maximum number of remotely initiated transfers MAXTASK Indicates the maximum number of transfers PRI Specifies the primary space allocation PSOUNIT Specifies the generic unit name used by the PSO interface when allocating temporary data sets PSOVOL Specifies the DASD volume used by the PSO interface when allocating temporary data sets REMAGE Specifies the queue purging interval in days for remotely initiated transfer requests SEC Specifies the default amount of secondary space allocated to new data sets in the units specified by the ALLOC parameter 5 Specifies whether SMF record is created at the completion of a transfer SMFNUM Designates the ID number for SMF records created by Unicenter CA XCOM Data Transport TCPSESS Indicates the maximum number of locally initiated TCP IP transfers to any one partner UNIT Specifies the default unit name when allocating new data sets USERD Specifies system wide user data to be included in the logging information for file transfers initiated by the system VOL Specifies the default volume serial number to be used when allocating new dat
306. me size PDSE Program Library Support Support for PDSE program library transfers requires PROGLIB YES in SYSINO1 and the use of an XCOMPRNT DD statement Any Unicenter CA XCOM Data Transport for z OS servers used to send or receive PDSE program library transfers must be modified to include the XCOMPRNT DD See sample member XCOM in the appendix Sample Files If PROGLIB YES is used in TYPE EXECUTE transfers then XCOMPRNT DD must be included in the batch XCOMJOB JCL Only whole PDSE program libraries may be transferred The transferring of an individual member or the use of wild cards for example ABC to transfer multiple members is not supported Unicenter CA XCOM Data Transport uses the values from PSOPREF and PSOVOL to create the temporary data sets used in transferring PDSE program libraries Generic File Specifications Using Wildcards 7 2 User Guide PDS member names can be specified generically for Send File and Receive File procedures by using wildcards To send or receive all members beginning with a particular prefix designate the Local File Name with that prefix followed by an asterisk For example PRIVATE LIB4 TRAN requests that members TRANUPDT TRANBKUP and TRANINQ be transferred To request that Unicenter CA XCOM Data Transport send all members of this PDS use PRIVATE LIB4 In generic specifications the asterisk must be the last character before the right parentheses In batch mode all members are transmi
307. menu option 2 5 SYSINO1 parameter 3 73 record format allocate new 2 44 transfers fixed to variable 7 7 RECSEP SYSINO1 parameter 3 60 relative record data sets 7 6 release file transfer request 3 74 RELEASE MODIFY command 6 33 REMAGE system parameter 6 17 REMFILE attribute label 2 116 remote group name Selection menu 2 7 list name Selection menu 2 8 system name Selection menu 2 7 Index 9 system user operator control parameter 2 112 indicator operator control parameter 2 111 transfers display with command line 6 36 6 49 unit Receive File From Another System screen 2 95 Send File screen 2 33 user name Selection menu 2 8 volume Receive File From Another System screen 2 95 Send File screen 2 33 remote system identification IP name or address 2 6 login user name 2 8 port 2 6 SNA LU Name 2 7 XCOM group name 2 7 XCOM list name 2 8 remote system information Receive File From Another System screen 2 92 remote systems AS 400 9 2 MVS 9 4 Novell NetWare 9 6 OpenVMS 9 8 OpenVMS Alpha 9 8 OpenVMS VAX 9 8 OS 2 9 10 Stratus System 88 9 12 Tandem 9 14 UNIX 9 17 VM 9 18 VSE 9 20 Windows 9 26 Windows NT 9 28 remotely initiated transfer requests queue purging interval 6 17 REMSUS status field 2 119 REMSYS attribute label 2 116 replace remote file 2 23 2 86 report title Send Report screen 2 54 REPORT SYSINO1 parameter 3 65
308. meter One of these two parameters must always be included in the SYSIN file History and SMF Files B 3 XCOMUTIL Parameters DATE PROCESS 4 User Guide Specifies the date of records that are to be purged from the history file Any history record written either on or before the specified date will be purged from the history file Value Definition yyddd Specifies the Julian date when records are to be purged from the history file Notes This parameter and the AGE parameter are mutually exclusive Both may not be included in the same SYSIN file Note that the purge date must be specified in terms of a two digit designation for the year and a three digit designation for the day of the year For instance 02100 represents year 2002 and the 100th day of that year Specifies that the object of XCOMUTIL is the history file Value Definition HISTORY Indicates that the object of XCOMUTIL is the history file Notes This parameter is required in the SYSIN file XCOMUTIL DD Statements XCOMUTIL DD Statements This section describes the DD statements that are needed to execute XCOMUTIL There are four DD statements required to execute XCOMUTIL DD Description Statement HISTIN A sequential file consisting of Unicenter CA XCOM Data Transport history records Generally the history file is reproduced as a sequential file prior to running XCOMUTIL Then HISTIN is used to input this file HISTOUT The sequential output
309. ministrator Destination Printer Information When sending a report to a Windows NT system specify the Destination parameter value or the Destination Printer field in the following form server name printer queue name Unicenter CA XCOM Data Transport limits the length of this field as indicated below The actual name on the destination system may be longer Type of transfer Specify Direct transfers using Version 2 Up to 21 characters protocols Indirect transfers or transfers using Up to 16 characters Version 1 protocols Remote System Information 9 31 Windows NT 2000 and XP Restrictions 9 32 User Guide Access to directories and files on drives formatted for NTFS can be controlled with the security features of Windows NT Access to all files on a Windows NT system can be controlled by the permissions set on a directory or file The access rights of the user ID on the remote system determine the actions permitted for the transfer Users cannot use a directory or file unless they have been granted the appropriate permissions Appendix A About SNA Logical Units This appendix explains the various logical unit LU types and discusses independent logical units ILUs and other pertinent issues Parts of a Network This section describes the parts of an SNA network LU Connections A logical unit LU is the addressable connection point into an SNA network with which an end user can send and receive mes
310. n New York that sends data directly to an output file The output data is transferred to a target DEC VAX system The application program writes an output file to the SYSOUT destination VAXBOSTN which is a VAX minicomputer located in the Boston office Unicenter CA XCOM Data Transport automatically sends this data to the VAX OUTBOUND JOB 2536 DEMO MSGCLASS D MSGLEVEL 1 STEP1 EXEC PGM SERPROG STEPLIB DD DISP SHR DSN USER LOADLIB DD1 DD DISP SHR DSN USER FILE ONE DD2 DD DISP SHR DSN USER FILE TWO NAXFILE DD SYSOUT A DEST VAXBOSTN The Remote Spooling Feature Process SYSOUT 5 7 Process SYSOUT Enhancements Process SYSOUT Enhancements This section describes process SYSOUT enhancements that you can use with Unicenter CA XCOM Data Transport External Writer Support You can set the WRITER operand equal to the name of an external writer instead of a destination name for when Unicenter CA XCOM Data Transport looks for reports to extract from the JES spool WRITER can be used with DEST To usea DEST and WRITER for a single LU you must define two groups with different group names for the same LU Reasons for Using the External Writer Sample Scenario 5 8 User Guide Reasons to use the external writer include the following m You do not need to define external writers to JES m Held output is processed immediately m External writers can facilitate the replacement of Network Job Entry NJ
311. n Unicenter CA XCOM Data Transport uses the LU 6 2 protocol it does not place hardware restrictions on the size of the data that it sends RJE based data transfer packages LU Type 1 limit the size of a data frame RU to 80 characters while 3270 based transfer packages LU Type 2 often limit the size to 1 920 characters the size of one screen LU 6 2 allows RU sizes of up to 65 536 characters Each transmitted string of data is wrapped in a protocol envelope Larger RU sizes such as those allowed with Unicenter CA XCOM Data Transport mean less protocol overhead and a higher percentage of actual data traveling across your communication links P Protocol Overhead Other LUs RJE etc P Data Data Data LU 6 2 CA XCOM Daa J JZ Support for Advanced Networking For SNA LU 6 2 fully exploits the PU Type 2 1 peer protocol This means that LU 6 2 is the only protocol that can use advanced functions such as Low Entry Networking LEN Advanced Peer to Peer Networking APPN and Independent Logical Units ILUs that are changing the face of computer networking today For more information about these topics see the appendix About SNA Logical Units APPC allows two programs running on distinctly different computers to converse with each other in real time without regard to hardware other protocols assume that one of the two devices communicating is a dumb terminal and impose all the limitations
312. n the Local File Name field For an indexed file the keys must not match those in the file on the local system or Unicenter CA XCOM Data Transport terminates the transfer with an error Unicenter CA XCOM Data Transport replaces the contents of a file on the local initiating system with the data being transferred If the file is indexed the records with matching keys are replaced and those with non matching keys are added When transferring a partitioned data set specify C only if the PDS itself is being created If a new member is being sent to an existing PDS specify for Replace The Menu Interface TSO ISPF Panels 2 85 Receive File From Another System Screen Record Separators EBCDIC Binary ASCII 2 86 User Guide If you do not override the default value and the file already exists on the target system the transfer terminates with an error Default C reate Specifies whether the receiving Unicenter CA XCOM Data Transport adds record separators line feed and or carriage return to delimit logical records Note Skip this field unless you are sending data to an ASCII computer Value Definition Y Unicenter CA XCOM Data Transport adds a record separator to delimit logical records N Unicenter CA XCOM Data Transport does not add record separators Default N Indicates the type of transferred data The computer from which the data are retrieved is responsible for performing any necessary conversion
313. names except IP values if Remote System ID filled in Limits the file transfers displayed to only those related to this remote system Value Definition Upto53 Specifies either a specific logical unit name a specific user a group characters name or an IP name or address The transfer is limited to this remote name Default remote system names Request Number Transfer ID Date Range Unicenter CA XCOM Data Transport Operator Control Value Definition Up to 6 numeric Limits the list to transfers that contain this specific request characters number Default request numbers Value Definition Up to 10 Limits the file transfers displayed to those that match this alphanumeric transfer ID characters Default All transfer IDs Specifies the period of time from which file transfer information is requested the year month and day as in 20040212 February 12 2004 Value Definition yyyymmdd For Start specifies the start date of the period from which file transfer information is requested For End specifies the end date of the period from which file transfer information is requested mm month dd day For example 20040212 indicates February 12 2004 Default m dates when both the start and end date are unspecified m Today s date when no end date is specified The Menu Interface TSO ISPF Panels 2 111 Unicenter CA XCOM Data Transport Transfer Request Display Screen
314. ndard file type discussed above the Save File format is also supported When you wish to send such a file to an AS 400 from a z OS system the file must exist on the target system prior to your transmission Additional Features 9 2 User Guide XQUE is a Unicenter CA XCOM Data Transport feature that allows the unattended transfer of reports from output queues to other Unicenter CA XCOM Data Transport nodes XQUE can select specific classes of reports based on the user job name form and so on from output queues XQUE also allows user and workstation groups to be equated to printer destinations on remote Unicenter CA XCOM Data Transport nodes You may use XQUE for example to get reports back to your host system that are generated on an AS 400 that you reach through IBM s HCF facility or between multiple AS 400s connected within a pass through environment AS 400 Configuration Issues If you are configuring the VTAM LU that represents the AS 400 on a mainframe make sure that the VTAM USS message 10 is not sent to that LU IBM s APPC software cannot start a session when this message commonly called the welcome message is sent To prevent this problem the VTAM or NCP USSTAB definition must be set to a table that does not have USSMSG10 The table that IBM originally provided with VTAM is a good alternative because it does not include message 10 Case Sensitivity Because the AS 400 is case sensitive you must enter
315. ndicates the type of transferred data The receiving computer is responsible for performing any necessary conversion Value B E A Default E Definition Indicates binary data Indicates that the data is in EBCDIC code Indicates that the data is in ASCII code Specifies how records exceeding the maximum logical record length LRECL are to be handled Value Definition Specifies that records larger than the maximum LRECL are to be N truncated to the maximum record length Specifies that Unicenter CA XCOM Data Transport is to terminate the file transfer upon receiving a record larger than the maximum LRECL The Menu Interface TSO ISPF Panels 2 55 Send Report To Another System Screen Code Table Writer Name 2 56 User Guide Default N Notes This field is supported only by the Unicenter CA XCOM Data Transport mainframe products Unicenter CA XCOM Data Transport for z OS Unicenter CA XCOM Data Transport for VSE and Unicenter CA XCOM Data Transport for VM When a record is truncated the data not within the LRECL limit is lost This is a 3 character alphanumeric field used for specifying the translation table to be used by the remote partner for this particular transfer only This field is applicable only for transfers to Unicenter CA XCOM UNIX or Windows 2000 2008 or XP partners and only if their INTERNAL CONVERSION TABLES NO Value Definition 1 to 3 bytes Specifies up to alphanumeric ch
316. nicenter CA XCOM Data Transport queue before purging The Unicenter CA XCOM Data Transport queue includes file transfer requests with future start dates transfer requests that have been placed on HOLD status and transfers that were suspended Unicenter CA XCOM Data Transport performs automatic queue purging at two times when the Unicenter CA XCOM Data Transport server comes up and daily at midnight Default Taken from Unicenter CA XCOM Data Transport Default Options Table Specifies the 1 to 3 character prefix to the file names atoe tab and etoa tab that contain the external ASCII to EBCDIC and EBCDIC to ASCII custom character conversion tables on the Unicenter CA XCOM Data Transport for Windows NT and the Unicenter CA XCOM Data Transport for UNIX platforms These custom character conversion tables determine which external translation tables are to be used when a transfer is sent to these platforms This parameter is valid only if INTERNAL CONVERSION TABLES NO is set on the receiving platform and the platforms are at r11 or above Value Definition 1to3 Specifies up to 3 alphanumeric characters identifying the code bytes table to be used by the remote partner Default None SYSINO1 Parameters CKPT Specifies the interval for checkpoints taken during a file transfer Value Definition 0to9999 Specifies the number of records to transfer for a checkpoint interval records Notes The checkpoint restart facility resumes int
317. nistrator Guide History records are written at all times for scheduled transfers History records are not written for TYPE EXECUTE transfers Transfers that Produce Records The following types of transfers will produce an SMF and history record m File transfers that complete successfully m File transfers that are manually canceled while inactive m File transfers that are automatically aged off the queue m File transfers that are terminated while in progress m File transfers that fail due to some kind of problem History and SMF Files B 1 XCOMUITIL History File Purge Utility Transfers That Do Not Produce Records Record Location The following types of transfers are not considered complete by Unicenter CA XCOM Data Transport and thus no SMF or history records are created for them m Suspended file transfers m File transfer requests that are in hold state The SMF record is mapped by the SMFDSECT macro which can be found in CAI CINBOMAC The history record is mapped by the HSTDSECT macro which can be found in CAI CINBOMAC XCOMUITIL History File Purge Utility B 2 XCOMUTIL is the Unicenter CA XCOM Data Transport utility that purges records from the Unicenter CA XCOM Data Transport history file This utility should be run periodically to prevent a history file full condition It has been designed as an offline utility because VSAM is inefficient at reclaiming space when records are randomly deleted from a VSAM
318. nments Any client node using Unicenter CA XCOM Data Transport can send and receive files from any of the remote systems shown in this example or any other Unicenter CA XCOM Data Transport component See Modular Support of Most Systems in the chapter Welcome in the Unicenter CA XCOM Data Transport for z OS Getting Started Linux 3 390 HL E z OS VSE VM Linux Intel VAX EE e APPC Window SHA Hetwork Tandem a Stratus j NetWare Windows NR Server Win 2000 Win XP Amm r EF Er Windows 05 2 Client cient NT Client NT Client Introduction 1 3 Network Levels in the SNA Model Network Levels in the SNA Model The End User Level An SNA network is divided into levels of physical and logical components The logical components are interconnected by a path control network that runs over the physical components As data is passed up and down the SNA functional layers each layer performs a set of control functions and adds control information to the data in the form of a header The headers do not change the information in the data but communicate with the next layer of SNA to ensure that the data is understood As the data is passed through the layers headers that are added at one end of the network are stripped off and read by the receiving end When the data reaches its final destination it is back to its original form The end user level consists of transaction programs li
319. nsport interfaces Partitioned Data Sets This section describes the level of support for partitioned data sets PDS partitioned data set extended PDSE and PDSE load libraries in Unicenter CA XCOM Data Transport PDS and PDSE Support Support for partitioned data sets including PDSE and program libraries is provided in Unicenter CA XCOM Data Transport Unicenter CA XCOM Data Transport reads the VTOC and the directory blocks to determine whether the file is a PDS and passes this information on to the remote system When a new file is created on the target system using the Create File option Unicenter CA XCOM Data Transport allocates the same amount of space for directory blocks there as it has on the source system The user can override this allocation by changing the number of directory blocks or reblocking the file through the appropriate SYSINO1 Batch Interface or File Allocation Information screen Menu Interface parameters Unicenter CA XCOM Data Transport transmits aliases if the member to which it is pointed is already on the target PDS Checkpointing should not be specified for transfer of PDSs Processing Different File Types 7 1 Generic File Specifications Using Wildcards Note Unicenter CA XCOM Data Transport reads the directory blocks for information such as alias relationships and pointers to preserve the integrity of the data therefore PDS files take longer to process than sequential or VSAM files of the sa
320. nter CA XCOM Data Transport for LAN Workstation accesses files from any Novell file server in a NetWare network server volume directory subdirectory filename Types of Files Supported Unicenter CA XCOM Data Transport for NetWare LAN supports standard NetWare file types 9 6 User Guide Novell NetWare Destination Printer Information Restriction When sending a report to a NetWare system specify the Destination parameter value or the Destination Printer field in the following form NW server name printer queue name Unicenter CA XCOM Data Transport limits the length of this field as indicated below The actual name on the destination system may be longer Type of transfer Specify Direct transfers using Version 2 Up to 21 characters protocols Indirect transfers or transfers using Up to 16 characters Version 1 protocols Unicenter CA XCOM Data Transport for NetWare LAN does not support library transfers to Novell NetWare systems Remote System Information 9 7 OpenVMS OpenVMS This section contains information about important aspects of the OpenVMS operating system Naming Conventions 9 8 User Guide Use the following format to name an OpenVMS Alpha file or an OpenVMS VAX file device directory filename type version The entire file specification can be a maximum of 255 characters The file type can be a maximum of 31 characters The following table describes the parts of an OpenVMS file n
321. nter XSHOW without an operand the resulting display lists remotely initiated file transfer requests If you select an individual request number XSHOW limits the display to only the XCOMPLEX Worker Servers that have the specified request number Additional details are NOT displayed For additional details enter the SHOW command from the XCOMPLEX Worker Server The display provides information about m Requests that are scheduled but not yet started m Active requests m Requests that were interrupted but are still eligible to be restarted for example requests that have not yet been completed purged or aged off the queue Important In large networks with a large number of queued transfers the output of this command can exhaust your WTO buffers Operation and Control 6 51 Using the Unicenter CA XCOM Data Transport MODIFY Commands Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name READ XCOM applsec XSHOW The applsec variable represents the value of the APPLSEC parameter in the Default Options Table XTRACE Command Format Operands Notes 6 52 User Guide For XCOMPLEX Worker Server and XCOMPLEX Admin Server only Activates a Unicenter CA XCOM Data Transport internal trace This trace must be activated individually on each server F XCOM X
322. ny non immediate queued procedure There may be a significant time lag between the request and its implementation For example the partner system may not sign on for an indeterminate period of time If a relative generation number is specified for a queued Unicenter CA XCOM Data Transport transfer and the GDG is updated before the transfer executes the wrong file may be transferred This would depend on whether the user wanted the file designated by the relative generation number at the time of the request or the most current generation of the file Unicenter CA XCOM Data Transport can accommodate either handling the transfer differently depending on whether the Batch or the Menu Interface is being used Scheduling a Transfer with GDG 0 Batch Interface 7 4 User Guide If you schedule a transfer with GDG 0 or GDG 0 specified the XCOM server resolves the filename to be the current GxxxxV00 number at the time the transfer is scheduled If you specify HOLD YES such as in an XTC scenario a relative generation number is used until the specific version is resolved This occurs just before the data set is opened The local file in a file transfer can be specified with the SYSINO1 LFILE parameter or the LCLDS01 DD statement see the chapter Batch Interface For TYPE SCHEDULE that is queued transfers Generation Data Groups are handled differently depending on the option used If the local file is specified with LCLDS01
323. o R12 Undefined R13 Address of register save area R14 Return address R15 Entry point address The following registers are available at exit Register Description RO to R14 Undefined R15 Return code The only valid return code is 0 for a normal return Return Code Description 0 Allow access immediately 4 Let the security package make the decision 8 Deny access immediately The following is a sample program using this exit CAI CINBOSAM XCOMEX12 Note In cases where a transfer causes the server to create a session due to GETSESS YES Exit 12 is called once before session establishment and once before the transfer is performed The exit is also called before each transfer restart User Exit 13 User Exit 13 Purpose This exit point controls command security both from the console and from the ISPF and CICS menu interfaces It executes a user written exit routine that verifies a given user s authority to issue a particular command The following are the possible results of the verification 1 The user is given access to the designated commands 2 The user is denied access to the commands 3 The user s right to access the commands is referred to the security package Module Name and Entry Point The module name and entry point for this exit is XCOMEX13 How to Enable Specify EXIT13 YES in the Default Options Table to enable this exit Calling Module The module XCOMOPRS calls this exit Entry Method This exit is a br
324. o site defined default values as obtained from the Unicenter CA XCOM Data Transport default table entered on the menu Special Feature Keys Special Feature Keys Help Facility Unicenter CA XCOM Data Transport screens permit the use of programmable function keys most of which are used in a manner consistent with ISPF Unicenter CA XCOM Data Transport uses standard ISPF Dialog Manager services and is compatible with the normal ISPF environment These include Key Definition PF1 Invokes online Help from a working screen When Help is active returns the user back to the original screen where Help was invoked PF2 Activates ISPF split screen mode PF3 Returns the user to the previous screen Input already entered on the current screen is saved If the current screen is the Primary Option Menu the user is returned to the ISPF panel from which Unicenter CA XCOM Data Transport was first invoked PF7 Scrolls backward up to continue the display for panels with multiple entries PF8 Scrolls forward down to continue the display for panels with multiple entries PF9 Swaps the current screen to the other screen in split screen mode PF10 Displays Japanese Character Set Support screen PF11 Invokes the File Transfer Scheduling Information screen allowing the user to enter file scheduling parameters PF12 Invokes the File Allocation Information screen from the Send MVS File To Another System screen allowing the user to o
325. ob Entry NJE system m be used by TSO users and for transactions within the following CICS IDMS Model 204 ROSCOE The Unicenter CA XCOM Data Transport server must be active if file transfers are to be queued The only transmissions that can be queued for transfer while the server is down are Process SYSOUT JES spool files Note PSO is not supported in the XCOMPLEX The XCOMPLEX Admin Server cannot be used to distribute PSO transfers requests While it is running the Unicenter CA XCOM Data Transport server continually scans the JES output queue for files to be sent to any of the destinations or writers defined in the Unicenter CA XCOM Data Transport control library that it services When Unicenter CA XCOM Data Transport recognizes work in its serviced JES destinations or writers it executes a file transfer to the targeted system Unicenter CA XCOM Data Transport can scan the JES spool for either a specific destination or an external writer An external writer can direct output to a specific printer on a remote system to permit a more detailed specification than is available when using RJE Basics of JES Spool Use You can use the destination parameter PSOWAIT to control whether output is pulled from the JES spool immediately and held in temporary data sets or is allowed to remain on the JES queue until a session is available to transmit it on For more information on the use of PSOWAIT see the secti
326. ocated on the remote system Value Definition 1 to 20 Specifies the number of units to be allocated on the remote system Default None Specifies the maximum number of volumes to be used in processing a multivolume output tape data set on the remote system Value Definition 1 to 255 Specifies the maximum number of volumes to be used in processing a multivolume output tape data set on the remote system Default None Specifies the sequence number of the first volume of a multivolume remote data set to be used Value Definition 1 to 255 Specifies the sequence number of the first volume of a multivolume remote data set to be used The Batch Interface 3 71 SYSINO1 Parameters SYSINO1 DCB Parameters BLKSIZE 3 72 User Guide Unicenter CA XCOM Data Transport allows the user to specify DCB information for files created or replaced locally or remotely by using the RECFM LRECL and BLKSIZE SYSINO1 parameters Users enter the DCB information when creating a file on the local system Under these circumstances the DCB information for the file transmitted is the default DCB information Specifying the RECFM LRECL and BLKSIZE parameters overrides the default DCB information The DCB information specifically the LRECL operand determines the maximum record length that the PC reads when receiving a binary file from MVS The local system confirms the accuracy of the three parameters When a z OS initiated receive is performe
327. ociated with the transfer request The user data is sent to all user exits and written to the history file upon completion of the file transfer For further information on how to use this user data with the Unicenter CA XCOM Data Transport user exits see the description of TDUDATA in General SYSINO1 Parameters in the chapter Batch Interface Value Definition XXXXXXXXXX One to ten alphanumeric characters of any type of data to be associated with a transfer request Allows the specification of transfer dependent user data This data is available to user exits in the RRDSUSER field of the RRDS data area mapped by the RRDDSECT macro while the transfer is pending or active The RRDSUSER field is defined by HDRDSECT within RRDDSECT Value Definition 1 to 10 bytes Specifies up to 10 bytes of data available to user exits during a file transfer Send MVS File To Another System Screen Remote System Information User ID Tape The Remote System Information fields of the Send MVS File To Another System screen pertain to the remote or non initiating Unicenter CA XCOM Data Transport partner Identifies the user ID under whose set of resource access privileges the file transfer is to execute on the remote system It should be a user ID known to the security system on that system Value Definition XXXXXXXXXXXX Specifies up to 12 alphanumeric characters representing a user ID whose access privileges on the remote system ar
328. of a particular terminal on the partner computer APPC and Unicenter CA XCOM Data Transport recognize that distributed processing employs intelligent processors so they can exploit the intelligence of the computers on which they are running Introduction 1 7 Unicenter CA XCOM Data Transport in the TCP IP Network Unicenter CA XCOM Data Transport in the TCP IP Network This section provides a discussion of the architectural and conceptual framework of the TCP IP communications protocol as it relates to the implementation of Unicenter CA XCOM Data Transport as a TCP IP application TCP IP Protocol Stack 1 8 User Guide TCP IP is a collection of specialized communications protocols and functions organized into a stack of four layers The layers that make up the TCP IP protocol stack are the following m Network layer the lowest protocol layer m Internetwork layer m Transport layer Application layer the highest protocol layer Each layer in the TCP IP protocol stack provides services to the layer above it and uses the services below it The following table lists the protocols and functions that form the content of each layer of the TCP IP protocol stack the table shows only partial contents for the top and bottom layer TCP IP Protocol Layer Network layer Internetwork layer Transport layer Application layer Protocols and Functions Token Ring Ethernet X 25 and so on Internet Protocol IP Control
329. of as a directory name filename The name of your file The following example uses a volume of CLX12 a subvolume of SCI and a file name of FILET CLX12 SCI FILE1 The Tandem file system is not a tree structure Each volume subvolume is independent that is it has no subvolumes above or below Tandem Types of Files Supported Unicenter CA XCOM Data Transport for Tandem supports the following file types through ENSCRIBE Tandem s disk file architecture m Edit files m Unstructured files m Entry sequenced files m Relative files m Key sequenced files for Replace only Unstructured files Unstructured files are large byte arrays Data in these files is accessed by using the relative byte address and the READ COUNT or WRITE COUNT parameters in the system procedure calls The application program determines the way in which they are used An EDIT file is a type of unstructured file signified by the file code 101 For more information about ENSCRIBE and unstructured files see the ENSCRIBE Programmer s Guide Structured files Unicenter CA XCOM Data Transport supports entry sequenced relative and key sequenced structured files m Entry sequenced files Entry sequenced files are sequential files Records are stored in the order in which they are entered These records are variable in length and cannot be added or deleted They are accessed by their record address m Relative files Relative files are ord
330. om Another System screen 2 94 Send File screen 2 32 Send Report screen 2 64 Submit Job screen 2 77 SYSINO1 parameter 3 34 dotted decimal notation 1 10 DSNTYPE SYSINO1 parameter 3 35 DSPRINT TSO command 5 1 DUMP MODIFY command 6 21 DUMPCL PARM parameter 3 13 system parameter 6 16 dumps 6 16 DUMPXCF MODIFY command 6 22 EBCDIC binary ASCII Receive File From Another System screen 2 87 Send File screen 2 24 Send Report screen 2 55 Submit Job screen 2 72 EDESC PARM parameter 3 13 3 16 system parameter 6 16 enable control library with command line 6 23 ENABLE MODIFY command 6 23 Index 3 end time Detailed File Transfer screen 2 121 entry sequenced data set 7 6 EPRTY SYSINOI parameter 3 36 EROUT PARM parameter 3 14 system parameter 6 16 ERRINTV system parameter 6 16 error flags reset 6 34 error handling 6 16 ESDS 7 6 EXEC PARM 4 1 statement 3 3 execute user exit routine from command line 6 25 execution priority alter with command line 6 8 Receive File From Another System screen 2 81 Send File screen 2 16 Send Report screen 2 48 Submit Job screen 2 66 exit points D 1 EXIT MODIFY command 6 25 EXPDT SYSINO1 parameter 3 67 Extended Remote File Name Entry screen 2 99 external writer 5 8 failed transfers resumption 3 11 FCB SYSINO1 parameter 3 65 file considerations fixed to variable record transfers 7 7 multivolume data sets 7 7 p
331. ome EBCDIC environment keyboards do not provide brackets In such cases use braces instead because Unicenter CA XCOM Data Transport will convert the braces to brackets If the file name is longer than 59 characters enter only a plus sign in the first position of this field Upon entering this value and completing all the fields of the screen the Extended Remote File Name Entry screen will be displayed This screen accepts file names of up to 256 characters For more information see Extended Remote File Name Entry Screen in this chapter The Menu Interface TSO ISPF Panels 2 21 Send MVS File To Another System Screen Remote File Substitution Character 2 22 User Guide Specifies a character that is used in a Remote File Name to establish a schema for generating a unique file name for each member involved in a partitioned data set PDS transfer The unique file name is derived by replacing the substitution character in the Remote File Name schema with the PDS member names Unicenter CA XCOM Data Transport generates a separate transfer request for each selected PDS member The PDS members to be transferred are selected from a member list which is displayed when a PDS name is entered without any member name in the Local File Name field For information about how to select a PDS member from a member list see Member Selection List in this chapter For example assume that from the partitioned data set XCOM PDS the members A
332. on RO Undefined R1 Address of EXO9PLST R2 to R12 Undefined R13 Address of register save area R14 Return address R15 Entry point address The following registers are available at exit Register Description RO to R14 Undefined R15 Return code The only valid return code is 0 for a normal return The following is a sample program using this exit CAI CINBOSAM XCOMEX09 User Exit 10 User Exit 10 Purpose This exit point allows execution of a user developed exit routine that generates a user designed banner page for all reports received by the system Module Name and Entry Point The module name and entry point for this exit is 10 How to Enable Specify EXIT10 YES in the Default Options Table to enable this exit Calling Module The modules XCOMRECV XCOMUPL2 XCOMUPL6 and XCOMUP F call this exit Entry Method This exit is a branch entry Required DSECT There is no required DSECT Addressing Mode at Entry The addressing mode at entry is 31 User Exits 0 21 User Exit 10 Registers at Entry Registers at Exit Valid Return Code Sample Program D 22 User Guide The following registers are available at entry Register R0 R2 R3 R4 R5 R6 R7 R8 R9 to R12 R13 R14 R15 Description Undefined Address of NSA control block mapped by NSADSECT macro Number of lines in each banner Number of letters per line Number of characters per letter Address of banner field Addr
333. on Using PSOWAIT in this chapter Note PSOWAIT is not a valid option for a TCP IP transfer Overview Sending Reports with PSO Setup Unicenter CA XCOM Data Transport for z OS scans the JES queue automatically for reports to transfer to remote partners Unicenter CA XCOM Data Transport selects reports either by WRITER or DEST The following criteria is required for setting up Unicenter CA XCOM Data Transport to send reports with PSO m There must be a destination member of TYPE DEST defined and enabled for the remote partner The destination member must contain one of the following DEST XCOM WRITER XCOM In the following sample XCOM represents the dest name or writer name that is specified for the report on the JES Spool An SNA address IP address or IP name may be specified in the dest member m The report must be queued to match the dest or writer name specified in the destination member It may be queued using an IEBGENER job or any other program that can queue the reports with the correct WRITER or DEST samples provided m If the destination is a TCP IP destination then TCPSESS must be set to at least 2 m Security must permit Unicenter CA XCOM Data Transport to access the reports on the spool The Remote Spooling Feature Process SYSOUT 5 3 Basics of JES Spool Use SAMPLE JCL to Queue Notes Unicenter CA XCOM Data Transport scans the JES Spool at the JESINTV specified in the Unicenter CA XCOM Data
334. on with remote system Display error End message Send data records Display error End message Send trailer Successful End transfer message Display error message End Introduction 1 13 The Menu Interface TSO ISPF Panels This chapter discusses the Unicenter CA XCOM Data Transport for z OS Menu Interface with its various screens and parameters Entering the Unicenter CA XCOM Data Transport Menu Interface Sample CLIST Access to Unicenter CA XCOM Data Transport s Primary Option Menu from ISPF is site dependent If Unicenter CA XCOM Data Transport is not an option on the ISPF Primary Option Menu or any subordinate ISPF menu screen you must include a procedure in your CLIST and use the following procedure 1 Choose Option 6 from the ISPF Primary Option Menu and press Enter to go to the command line mode 2 Type XCOM62 CA XCOM on the command line and press Enter to invoke Unicenter CA XCOM Data Transport PROC 0 DEBUG CONTROL END DEND IF amp DEBUG NE THEN CONTROL LIST CONLIST SYMLIST RR KK KK RK KK KK KK KK KKK START ISPEXEC LIBDEF ISPPLIB DATASET ID XCOM RBO CINBOSPL ISPEXEC LIBDEF ISPMLIB DATASET ID XCOM RBO CINBOSML STEPLIB DSNAME XCOM RBO0 LOADLIB ISPEXEC LIBDEF ISPTLIB DATASET ID XCOM RBO CINBOSTL amp SYSUID ISPF ISPPROF ALTLIB ACTIVATE APPLICATION CLIST DA XCOM RBO CINBOSCL ISPEXEC SELECT PANEL XCOMPRIM NEWAPPL XCOM PASSLIB ISPEXEC LI
335. ons Main Coding Rules The SYSINO1 parameters must be coded according to the same rules that are used in coding standard SYSIN instream information Thus among the most important rules to be observed when coding SYSINO1 parameters are the following m Parameter data can span multiple lines as long as a plus sign is placed at the end of each line to be continued and that the continuation line starts in columns 2 through 16 m Each new parameter must start in column one m Parameter values with embedded spaces quotes or a plus sign followed by a space which would indicate a continuation line must be enclosed in either single or double quotes Preserving 5 5 01 Information If you want the 5 01 parameters for a file transfer to be included in the Unicenter CA XCOM Data Transport activity log code the PARM parameter LOG YES on the EXEC card of the JCL for the transfer The Batch Interface 3 29 SYSINO1 Parameters General SYSINO1 Parameters AGE CODETABL 3 30 User Guide Unless otherwise noted the parameters described in the following are optional Overrides the Unicenter CA XCOM Data Transport default age purging interval Value Definition 1 to 999 Specifies the number of days that a transfer request can remain in days the queue before being purged Notes Aging is relative to the scheduled start date of the file transfer The purging interval is the number of days a request can remain on the U
336. or all parameter definitions F XCOM INQ MAX DFLT The following operands are used with the INO command Operand Description MAX Displays the current values for MAXTASK MAXLOC MAXREM and TCPSESS DFLT Displays the current values for all XCOMDFLT parameters that are currently in use by the Unicenter CA XCOM Data Transport server The initial values of the MAXTASK MAXLOC MAXREM and TCPSESS parameters are defined in the Unicenter CA XCOM Data Transport Default Options Table These values can be altered by using the DFLT command Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name READ XCOM applsec INQ The applsec variable represents the value of the APPLSEC parameter in the Default Options Table Operation and Control 6 27 Using the Unicenter CA XCOM Data Transport MODIFY Commands LIST Command Format Operands Notes Displays all of the information pertaining to a Unicenter CA XCOM Data Transport control library member F XCOM LIST membername The following operand is used with the LIST command Operand Description membername Specifies the name of the Unicenter CA XCOM Data Transport control library member the contents of which are to be displayed The member name can contain up to eight alphanumeric characters An asteris
337. ote ISPF and CICS display requests may cause resource checking for both SHOW and RSHOW commands Operation and Control 6 37 Using the Unicenter CA XCOM Data Transport MODIFY Commands SHOW Command Format Operand Notes 6 38 User Guide Displays information about locally initiated file transfer requests F XCOM SHOW nnnnnn des tname The following operands are used with the SHOW command Operand Description nnnnnn Specifies the number 0 to 999999 of the transfer request about which information is to be displayed destname Specifies the name of the destination whose locally initiated transfers are to be displayed Any of the following items can be used as a destination name mg SNA LU name m TCP IP name m TCP IP address Note Entered without an operand the SHOW command displays all locally initiated file transfer requests However more information is displayed for a transfer that is selected individually than when showing all transfers The display provides information about m Requests that are scheduled but not yet started m Active requests m Requests that were interrupted but are still eligible to be restarted for example requests that have not yet been completed purged or aged off the queue Important In large networks with a large number of queued transfers the output of this command can exhaust your WTO buffers Using the Unicenter CA XCOM Data Transport MODIFY Commands Command Securit
338. oth label components Value Definition sequence number This value identifies the sequence number of a data set 0001 to 9999 on tape Default 0001 processing type Represent the types of processing to be applied to data AL AUL BLP pp oP ape NL NSL SL SUL Default none Default 1 SL Notes Unicenter CA XCOM Data Transport writes only standard label tapes This parameter should be specified in the same way that the LABEL parameter appears in the JCL see the following example Example LABEL 2 BLP This specification refers to the second data set on the tape The type of processing to be applied to this data set is BLP LLABEL LUNITCT SYSINO1 Parameters Specifies the sequence number of the file on the tape volume to be used for the local data set and the type of processing to be applied to the data set sequence number processing type Valid values that can substitute for these variables are listed in the following table Value Definition sequence 1 to 9999 number This value identifies the sequence number of a data set on tape processing AL AUL BLP LTM NL NSL SL SUL type Represents the types of processing to be applied to data sets on tape Notes This parameter should be specified in the same way that the LABEL parameter appears in the JCL Default 1 SL Example LLABEL 2 BLP This specification refers to the second data set on the tape The type of processing to be
339. out abort 3 27 TIMEOUT parameter 3 25 XCOMJOB 3 3 XCOMREST DD statement 3 7 TYPE INQUIRE return code 3 82 sample transfer through XCOMPLEX Admin Server C 28 transfers 3 39 XCOMJOB 3 3 3 4 TYPE RECEIVE FILETYPE requirement 3 54 TYPE SCHEDULE return code 3 82 sample transfer C 25 sample transfer through XCOMPLEX Admin Server C 26 transfers 3 19 3 23 3 43 XCOMINQ DD statement 3 7 XCOMJOB 3 3 3 4 UID attribute label 2 116 Unicenter CA XCOM Data Transport and SNA network 1 4 and TCP IP network 1 8 benefits of LU 6 2 APPC 1 6 connectivity 1 3 control library alternate 2 11 invoking 1 1 menu interface 1 1 programming interface 1 2 MODIFY commands format 6 4 usage 6 4 process control user exit D 19 server starting 6 1 unit Receive File From Another System screen 2 95 Send File screen 2 33 UNIT SYSINO1 parameter 3 61 system parameter 6 17 UNITCT SYSINOT parameter 3 71 UNIX 9 17 UNKN status field 2 119 unprotected fields 2 117 usage statistics 6 32 user execute user written exit routine from command line 6 25 exits D 1 ID Receive File From Another System screen 2 96 Send File screen 2 34 Send Report screen 2 30 2 61 2 63 2 92 Submit Job screen 2 75 2 78 name Selection menu 2 8 USER ID attribute label 2 116 USER SYSINO1 parameter 3 54 USERD system parameter 6 17 USERID SYSINO1 parameter 3 54 user specified checkpoints 3 2 Index 15 V
340. p directory Range 1 to 32 characters filename Required The name of the Stratus file Range 1 to 32 characters suffix A file classification You can have multiple suffixes at the end of a file name Each suffix starts with a period The following table describes some common Stratus suffixes File type Suffixes Examples source pll cobol payroll c application cobol object obj payroll obj application obj list list payroll list application list error error payrolLerror application error program payroll pm application pm module command cm start_up cm macro compile_and_bind cm back up backup payroll c backup 9 12 User Guide Stratus Types of Files Supported Additional Features Restrictions Stratus supports the following file types for remotely initiated transfers Fixed This type of file contains records of the same size Each record is stored in a disk or tape region holding a number of bytes that is the same for all the records in the file Sequential This type of file contains records of varying sizes in a disk or tape region holding approximately the same number of bytes as the record for example the record storage regions vary from record to record Records can only be accessed on a record by record basis The following are additional features of Unicenter CA XCOM Data Transport for Stratus of which you should be aware Security option Unicenter CA XCOM Data Transport
341. pe Value Definition 1to4 Specifies the density to be used in creating a tape Specifies the number of volumes to be used in processing a multivolume output tape data set Value Definition 1 to 255 Specifies the number of volumes to be used in processing a multivolume output tape data set Expiration Date File Allocation Information Screen Specifies the date when the data set is to be purged from tape Value Definition yyddd Specifies the expiration date of the tape data set The expiration date is indicated with a two digit designation for the year and a three digit designation for the day of the year For instance the expiration date 03021 represents year 2008 and the 21st day of that year yyyy ddd Specifies the expiration date of the tape data set The expiration date is indicated with a four digit designation for the year and a three digit designation for the day of the year For instance the expiration date 2003 021 represents year 2003 and the 21st day of that year 1 to 9999 Specifies the number of days the data set is to be retained For instance 30 means that the data set is to be kept for 30 days before being purged from tape File Allocation Information Screen The File Allocation Information screen is used to specify allocation parameters for a new data set The parameter available on the File Allocation Information screen corresponds to standard z OS data set allocation definitions This screen
342. port security interface see the chapter Overview of Unicenter CA XCOM Data Transport Security To send a blank parameter value to the remote system enter inserting at least one blank space between the quotation marks Do this when the remote system supplies its own default value for the user ID under whose access privileges the file transfer is to execute on the remote system Many systems do not perform security checking on reports If this is the case skip this and the Remote Password parameter Default The last remote user ID entered The Menu Interface TSO ISPF Panels 2 61 Send Report To Another System Screen Password Notify User 2 62 User Guide Identifies the password associated with the remote user ID This value is not displayed Value Definition Up to 31 Specifies up to 31 alphanumeric characters representing the alphanumeric remote user s password characters Notes If the remote system is running IBM eTrust CA ACF2 Security or eTrust CA Top Secret Security you can also use this parameter to change the password on the remote system by using this format oldpassword newpassword Identifies the user on the remote system Unicenter CA XCOM Data Transport is to notify once the transfer completes Value Definition user id If any value but LOG is given Unicenter CA XCOM Data Transport interprets this as a specific user ID on the remote system If this user is not logged on when t
343. r Identifies the Windows 2000 2003 or XP domain associated with the remote server Value Definition Up to 15 Specifies up to 15 alphanumeric characters representing the alphanumeric domain user password and ID associated with the remote characters server Notes Can only be used for transfers running under Windows 2000 2003 or Identifies the user on the remote system Unicenter CA XCOM Data Transport is to notify once the transfer completes Value Definition LOG Indicates that the main operator on the remote computer be notified If the remote computer is a z OS system a WTO macro is issued by Unicenter CA XCOM Data Transport On an AS 400 or a VAX system the operator console is notified User_id If any value but LOG is given Unicenter CA XCOM Data Transport interprets this as a specific user ID on the remote system If that user is not logged on when the transfer completes the message is displayed the next time the user logs on Default LOG The Menu Interface TSO ISPF Panels 2 93 Receive File From Another System Screen Volume Unit 2 94 User Guide Indicates the volume on the remote system on which the file is to be created or resides for existing non cataloged files Value Definition XXXXXX Specifies the name of the volume serial where the remote data set may be found or created This value can be up to six alphanumeric characters Default The volume name determined by the remote sys
344. r Member XCOMJOXS Sample XCOMJOB Schedule JCL through the XCOMPLEX Admin Server Member XCOMJOXS This member contains a sample XCOMJOB Schedule JCL through the XCOMPLEX Admin Server CAI CINBOSAM XCOMJOXS found on the distribution tape This illustrates for a TYPE SCHEDULE transfer through the XCOMPLEX Admin Server JOBNAME JOB ACCOUNTING NAME CLASS A MSGCLASS X a none ese A mM eS tS NOTE THE PARM STATEMENT MAY ALTERNATIVELY BE SPECIFIED AS PARM TYPE SCHEDULE DFLTAB XCPTDFBO WHERE DEFAULT TABLE XCPTDFBO HAS CORRECT ADMIN ACBNAME PARAMETERS THIS STEP USES XCOMJOB TYPE SCHEDULE TO INITIATE A FILE TRANSFER VIA THE XCOMPLEX ADMIN THE XCOMPLEX ADMIN WILL ROUTE THE i TRANSFER TO THE BEST AVAILABLE XCOMPLEX WORKER SERVER XCOMJOB WILL PROVIDE A RC BASED ON THE SUCCESSFUL SCHEDULING OF A TRANSFER TO AN XCOMPLEX WORKER XCOMJOB WILL RETURN BOTH A GLOBAL REQUEST NUMBER FROM THE XCOMPLEX ADMIN AND A LOCAL REQUEST NUMBER FROM THE XCOMPLEX WORKER IS THE ACBNAME OF THE XCOMPLEX ADMIN rrt EE REMIT EP STEPO1 EXEC PGM XCOMJOB PARM TYPE SCHEDULE ACBNAME XCPT DFLTAB XCOMDFLT STCAPPL XCPT 11 STEPLIB DD DSN CAI CAILIB DISP SHR
345. r Data 2 60 User Guide Allows the user to specify up to 10 bytes of any type of data to be associated with the transfer request The user data is sent to all user exits and written to the history file upon completion of the file transfer Value Definition Up to 10 Specifies data to be associated with the transfer request alphanumeric characters Allows the specification of transfer dependent user data This data is available to user exits in the RRDSUSER field of the RRDS data area mapped by the RRDDSECT macro while the transfer is pending or active The RRDSUSER field is defined by HDRDSECT within RRDDSECT Value Definition 1 to 10 bytes Specifies up to 10 bytes of data available to user exits during a file transfer Send Report To Another System Screen Remote System Information User ID The Remote System Information parameter fields of the Send Report screen are described in the following Identifies the user ID under whose set of resource access privileges the transfer is to execute on the remote system Make this a user ID known to the security system resident on the remote system Value Definition Up to 12 Specifies the user ID under whose set of resource access alphanumeric privileges the transfer is to execute on the remote system characters Notes For a third party file transfer this parameter provides the user ID for the target remote system For more information about the Unicenter CA XCOM Data Trans
346. r contains the CICS TCT entries to run the Unicenter CA XCOM Data Transport CICS MVS interface If you create the TCT entries through the COPYCSD step which copies directly from the Unicenter CA XCOM Data Transport provided CSD to the user CSD this member is not required If you do not use the COPYCSD step you must copy these entries into the CICS TCT and assemble the TCT before Unicenter CA XCOM Data Transport can be used oes Es UD scs vac HOG oot et pack rote a 28 XCOM CICS ENTRIES ENTRY BE BUILD FOR EACH ADDRESS SPACE THAT CICS COMMUNICATES WITH DFHTCT TYPE SYSTEM ACCMETH VTAM NETNAME XCOMAPPL gt POINTS TO VTAM APPLID FOR XCOM MODENAM XCOMMODE gt POINTS TO MODENAME FOR XCOM SYSIDNT XCM1 gt USE ANY VALID NAME HERE FEATURE SINGLE BUFFER 1024 gt lt gt lt gt lt gt x gt x gt x RUSIZE 1024 TRMSTAT TRANSCEIVE Sample Files 41 Appendix User Exits Unicenter CA XCOM Data Transport user exits allow users to modify characteristics and capabilities of Unicenter CA XCOM Data Transport software by inserting their o
347. r in the Default Options Table m destname the ipname or luname for which the trace is to be turned off NOXTRACE Command For XCOMPLEX Worker Server or XCOMPLEX Admin Server only Deactivates the trace function Format F XCOM NOXTRACE Operands None Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec NOXTRACE The applsec variable represents the APPLSEC parameter in the Default Options Table Operation and Control 6 31 Using the Unicenter CA XCOM Data Transport MODIFY Commands NSASTAT Command Provides usage statistics that may be requested by Unicenter CA XCOM Data Transport Technical Support Format F XCOM NSASTAT Notes The following statistics are displayed NSA NSAX NSAI NSAA NSAR LCUR LMAX RCUR RMAX Command Security Requirements Number of elements in the Network Session Anchor NSA Block chain Number of free elements in the NSA chain Number of inactive elements in the NSA chain Number of active elements in the NSA chain Number of elements in the dispatch chain Number of locally initiated elements that are currently active Peak number of locally initiated elements Number of remotely initiated elements that are currently active Peak number of remotely initiated elements
348. r in the Default Options Table Operation and Control 6 29 Using the Unicenter CA XCOM Data Transport MODIFY Commands NOTRACE Command Deactivates the trace function Format F XCOM NOTRACE Zuname 7pname Operands The following operands are used with the NOTRACE command Operand Description asterisk Specifies that all active traces are to be turned off F XCOM NOTRACE and F XCOM NOTRACE have the same result luname Specifies the name of the LU for which the trace is to be turned off The LU name can contain up to eight alphanumeric characters Note This operand is invalid in the TCP IP protocol environment When a trace is closed z OS create a spin off data set that is printed as soon as the SYSOUT file is closed The file is closed and dynamically deallocated when NOTRACE is specified or when there are no longer any active traces Use the TRACE command to activate traces ipname Specifies the name or address of the IP destination for which the trace is to be turned off 6 30 User Guide Using the Unicenter CA XCOM Data Transport MODIFY Commands Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec NOTRACE destname The variable represents the following value m applsec the APPLSEC paramete
349. r tracking and control functions through the menu interface Do not confuse LUSER with the USERID parameter USERID refers to the authorization access ID on the target system both for ordinary file transfers and third party initiated transfers Default The ID associated with the address space created when the file transfer request is made Specifies the one to eight character name of the management class to use when allocating a new SMS managed data set Note This parameter applies only to mainframe SMS data sets Default None Indicates the beginning of a new file transfer definition Unlike all other SYSINO1 parameters no value is assigned to this parameter The parameter NEWXFER is entered in SYSINO1 at a point where a new transfer request is defined The text following the parameter name NEWXFER up to the next occurrence of NEWXFER if any forms the definition of a transfer request Notes At least one parameter must be specified between succeeding NEWXFER parameters To negate a previously specified parameter specify the parameter again with no value It is not necessary to respecify all parameters for an additional file transfer only those that are different All parameters other than XTC parameters are propagated For example if two TYPE SEND transfers are requested then the FILE remote file name parameter is usually specified twice but the FILETYPE FILE and TYPE SEND parameters have to be specified only for the firs
350. rameter is ignored 3 32 User Guide COMPRESS SYSINO1 Parameters Specifies whether Unicenter CA XCOM Data Transport compresses the data being transferred and decompresses it on the remote system Compressing the data decreases the transmission time on lower speed links Value Definition YES Provides Run Length Encoding RLE for blanks and binary zeros only YES is the default NO No data compression RLE Provides complete Run Length Encoding for all characters COMPACT Provides full RLE as in RLE above plus a byte compaction scheme that is suitable for uppercase English text COMPACTL Same as COMPACT above only the compaction scheme is most beneficial for lowercase English text LZSMALL Unicenter CA XCOM Data Transport compresses the data according to the small memory model of Lempel Ziv 77 compression LZMEDIUM Unicenter CA XCOM Data Transport compresses the data according to the medium memory model of Lempel Ziv 77 compression LZLARGE Unicenter CA XCOM Data Transport compresses the data according to the large memory model of Lempel Ziv 77 compression HUFFMAN Greater compression than RLE but not as much as the Lempel Ziv 77 modes LZRW3 General purpose algorithm that runs fast and gives reasonable compression ZLIB n Greater compression than LZRW3 but less than LZSMALL LZMEDIUM and LZLARGE The n value can be 1 through 9 Default YES The Batch Interface 3 33 SYSINO1 Parameters DATACLAS DOMA
351. ransfer For more information see Remote File Name and Member Selection List in this chapter Default The last data set name entered Specifies the sequence number of the data set on tape Note Leave the field blank for disk files Value Definition 1109999 Specifies the sequence number of the data set on tape The Menu Interface TSO ISPF Panels 2 49 Send Report To Another System Screen Label Type Unit Count Volume Sequence 2 50 User Guide Specifies the type of processing to be done on the tape data set Note Leave the field blank for disk files Value Definition SL Specifies the tape processing type SL NL Specifies the tape processing type NL NSL Specifies the tape processing type NSL SUL Specifies the tape processing type SUL BLP Specifies the tape processing type BLP LTM Specifies the tape processing type LTM AL Specifies the tape processing type AL AUL Specifies the tape processing type AUL Specifies the number of tape units to be allocated on the system Note Leave the field blank for disk files Value Definition 1 to 20 Specifies the number of the units to be allocated on the system Specifies the sequence number of the first volume of a multivolume tape data set to be used Note Leave the field blank for disk files Value Definition 1 to 255 Specifies the sequence number of the first volume of a multivolume data set to be used Send Report To Another System Screen Secur
352. relative generation numbers are normally not updated by z OS until the end of the associated job Therefore if the Unicenter CA XCOM Data Transport started task is being used to update the generation data set its relative generation number would not be updated until the started task is brought down This generation data set could be updated multiple times before the Unicenter CA XCOM Data Transport started task is stopped the second update being as far as z OS is concerned to the 2 generation the third to the 3 generation and so on The situation described above is generally undesirable Unicenter CA XCOM Data Transport avoids this by treating each Generation Data Group file transfer request as if it were an autonomous job This allows for the relative generation of number references in the conventional manner no matter when the Unicenter CA XCOM Data Transport started task is brought down The complete data set name of a generation data set including the 00 suffix is sent in Unicenter CA XCOM Data Transport messages to partner systems version 2 transfers only For example error and log messages concerning a generation data set sent to a PC or workstation display the actual z OS data set name provided the transfer is a version 2 transfer Processing Different File Types 7 3 Generation Data Groups Scheduled Versus Immediate Transfer Considerations Generation data sets introduce a complicating factor into a
353. rent file transfer fails Value Definition Up to 8 transfer Specifies up to eight transfers the HOLDCOUNT request names parameter of which is to be incremented if the current file transfer fails Notes A VTAM communications error does not count as a failure XTCERRPURGE Specifies the transfer requests to be purged if the transfer concludes unsuccessfully Value Definition Up to 8 transfer Specifies up to eight transfers to be purged if the current request names file transfer concludes unsuccessfully XTCGOODDECR Indicates an XTCNET job whose hold count decrements if the file transfer completes successfully Value Definition Up to 8 transfer Specifies up to eight transfers the HOLDCOUNT parameter request names of which is to be decremented if the current transfer completes successfully Notes If the current file transfer completes successfully the value of the HOLDCOUNT parameter of the transfers assigned to this parameter is reduced by 1 unless the next transfer has already started or the HOLDCOUNT value has already reached zero 3 76 User Guide XTCGOODINCR XTCGOODPURGE XTCGOODREL XTCJOB SYSINO1 Parameters Indicates the transfer requests whose HOLDCOUNT parameter is incremented when the current file transfer completes successfully Value Definition Up to 8 transfer Specifies up to eight transfers whose HOLDCOUNT request names parameter is to be incremented if a transfer completes successfully Specifies t
354. require that the computers participating in a data exchange acknowledge the reception of the transmitted data The reliability of communication is implemented at the next higher protocol layer The protocols of the Transport layer allow communication between application programs The Transmission Control Protocol of this layer establishes a connection between the sender and receiver and provides a continuous communication service with reliability of transmissions TCP divides the data to be transmitted into smaller units packets datagrams sends them individually using IP and reassembles them at the destination node comparing the received data with the data that were sent TCP is capable of determining if the two are the same If they are not that is data were lost or damaged during transmission TCP resends the missing data Introduction 1 9 Unicenter CA XCOM Data Transport in the TCP IP Network Application Layer The Application layer which is built on the services of the Transport layer provides a number of applications that allow users to use network services terminal to terminal communication data transfer electronic mail and so on The Application layer provides an application programming interface known as Sockets for communications applications Unicenter CA XCOM Data Transport uses this component of the Application layer to transfer files to machines in a TCP IP network Secure Socket Layer SSL The S
355. rker server connected to an XCOMPLEX Admin Server The statistics displays information such as the number of remotely initiated transfers locally initiated transfers and how many are TCP IP transfers It also displays activity like how many transfers are held suspended remotely suspended retry pending and or inactive The display also shows XCOMPLEX Worker Servers who are not currently connected to the XCOMPLEX Admin Server This data from the STAT command is refreshed on the XCOMPLEX Worker Server side every 30 seconds so this display should only be used for general monitoring of the XCOMPLEX Worker Servers and their workload distribution F XCOM STAT None Command Security Requirements 6 40 User Guide The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name READ XCOM applsec STAT The applsec variable represents the APPLSEC parameter in the Default Options Table Using the Unicenter CA XCOM Data Transport MODIFY Commands Example The following is an example of the STAT command output for three XCOMPLEX Worker Servers connected to an XCOMPLEX Admin Server and an XCOMPLEX Worker Server that is not currently connected A26IXCOM HAS RECEIVED STAT COMMAND A26RXCOM HAS RECEIVED STAT COMMAND A26UXCOM HAS RECEIVED STAT COMMAND A26LXCOM IS NOT CONNECTED TO THE XCOMPLEX STAT COMMAND PROCESSING
356. rocessing different file types 7 1 replacement Receive File From Another System screen 2 86 security overview 8 1 transfers dependent scheduling 3 74 File Allocation Information screen 2 42 parameter fields 2 43 Index 4 User Guide file replacement Send File screen 2 23 file sequence Submit Job screen 2 67 File Transfer Display Select screen 2 109 File Transfer Scheduling Information screen 2 102 member selection list 2 107 parameters 2 103 FILE SYSINO1 parameter 3 56 FILEOPT SYSINO1 parameter 3 57 FILETYPE SYSINO1 parameter 3 36 FILETYPE FILE parameters LUNIT 3 58 LVOL 3 58 PACK 3 59 SPACE 3 60 UNIT 3 61 FILETYPE REPORT parameters See also SYSINO1 parameters CHARS 3 62 CLASS 3 62 CONTROL 3 63 COPY 3 63 DEST 3 64 DISP 3 64 FCB 3 65 FORM 3 65 REPORT 3 65 REPORTHOLD 3 66 WRITER 3 66 flags reset error flags 6 34 form type Send Report screen 2 54 FORM SYSINO1 parameter 3 65 forms control buffer 2 57 function keys 2 3 trace parameters 6 47 G generation data groups 7 3 transferring all generations 7 5 generic file specifications 7 2 unit allocate new 2 43 global data set defining C 9 GROUP PARM parameter 3 15 SYSINOI parameter 3 37 H halt file transfer with command line 6 45 heading line Detailed File Transfer screen 2 121 HELD status field 2 118 Help facility 2 3 HISTIN DD statement B 5 history files sample JCL to create
357. rol Block DCB parameters m Block size m Logical record length m Record format m Volume m Unit For more information regarding any of these fields see the IBM JCL reference manual Remote System Information 9 5 Novell NetWare Additional Features You should be aware of the following additional features of Unicenter CA XCOM Data Transport for z OS m CICS interface Turn this on by indicating that you wish to notify CICS in the appropriate remote system notify field in your version of Unicenter CA XCOM Data Transport To do this provide the VTAM APPLID of the CICS system in the related ID field Your z OS or CICS application development team can provide you with this Invoking this interface should start a CICS transaction program following the successful completion of a transfer if one has been provided at the host m Store and forward Perform transfers between two nodes connected to an intermediate z OS system by invoking the indirect transfer feature in your version of Unicenter CA XCOM Data Transport This asks you for the final destination LU name and sends a transfer in two stages The first stage goes to the z OS JES spool where it waits for the final destination to be connected before the second stage occurs Novell NetWare This section contains information about important aspects of the Novell NetWare operating system Naming Conventions Use the following format to name a Netware file Note Unice
358. rs with any value in that field will be displayed Note You must fill in one of these parameter fields to access the history log Do not press ENTER until you fill in at least one of these fields If you get a fatal VTAM error while attempting to communicate with the Unicenter CA XCOM Data Transport server history log information will not be displayed Note Be specific in filtering the information displayed This is especially advisable at sites where there is considerable Unicenter CA XCOM Data Transport activity Otherwise screen displays could be cluttered with masses of irrelevant information The Menu Interface TSO ISPF Panels 2 109 Unicenter CA XCOM Data Transport Operator Control Parameters Requesting User ID The parameters that can be entered on this screen are described below Limits the file transfer requests displayed to those requested under the authority of the specified user ID Value Definition Up to 12 Specifies the user ID that requested the transfers you want alphanumeric to display characters Default TSO user ID Remote System TCP IP Remote System ID 2 110 User Guide Indicates the value specified in the Remote System ID field Value Definition Y es Specifies that the value in the Remote System ID field represents an IP name or address N o Specifies that the value in the Remote System ID field represents a specific logical unit name user or group Default All remote system
359. ry that does not exist Unicenter CA XCOM Data Transport for Windows creates the directory for you Note If you do not specify a directory the default current directory is used filename Required q The name of the data file Range 1 to 8 characters for Windows 98 The path for the file name may be up to 256 bytes Windows 98 Part Description ext The file extension used to further identify the file Executable programs must use the extension EXE or COM Range 1 to3 characters Note If you do not specify an extension Unicenter CA XCOM Data Transport does not supply a default Restrictions The following restriction applies to Unicenter CA XCOM Data Transport for Windows m APPC restrictions Due to the vast number of vendor APPCs and link types supported by Unicenter CA XCOM Data Transport consult the APPC vendor s manual for restrictions on the services provided by that vendor These restrictions may impact such features as z OS TYPE EXECUTE transfers environments to which you can send etc m This is a single user system Do not send multiple simultaneous transfers to this partner Remote System Information 9 27 Windows NT 2000 and XP Windows NT 2000 and XP This section contains information about important aspects of the Windows NT 2000 and XP operating systems Naming Conventions 9 28 User Guide Unicenter CA XCOM Data Transport for Windows NT supports the standard Windows NT file names
360. s be either the file being data set involved in this transferred to the remote computer or transfer the name of the data set in which Unicenter CA XCOM Data Transport will store the data received from the remote computer Define this data set using either the LCLDS01 DD statement or the SYSINOI file s parameter Note If both are specified the data set defined by LFILE takes precedence The file that passes parameters These instructions include whether this is to Unicenter CA XCOM Data an inbound or outbound transfer and Transport whom to notify on the remote system when the transfer is completed The DDNAME for this file is SYSINO1 Allocate these two files to your job through JCL DD statements or by dynamic allocation You will probably only use the dynamic allocation method for interactive or Assembler programs Sample DD Statement The following is a sample DD statement allocating LCLDS01 LCLDSO1 DD DISP SHR DSN LOCAL FILE NAME SYSINO1 DD DISP SHR DSN PARM FILE NAME The Programming Interface 4 3 Calling Unicenter CA XCOM Data Transport from a COBOL Program Calling Unicenter CA XCOM Data Transport from a COBOL Program Sample Fragment 4 4 User Guide Use the COBOL verbs CALL and CANCEL to load and delete the Unicenter CA XCOM Data Transport modules in your address space Before making the call to Unicenter CA XCOM Data Transport make sure that the files SYSINO1 and LCLDS01 have b
361. s File Considerations 2 7 7 Fixed to Variable Length Record Transfers 1 7 7 Multivolume Data sets 7 7 Spanned Records eee ne eda s der bon ode lu don ab e o cr ab dudes 7 7 Chapter 8 Overview of Unicenter CA XCOM Data Transport Security File SCC HELD 25 8 1 Command ns n eee 8 1 8 1 dcs RM E do At pd ant 8 2 Data Encryption Using Secure Socket Layer SSL 8 2 Chapter 9 Remote System Information 9 2 Naming Conventions sssr cedar eid ug ex sies aie ae 9 2 Types of Files Supported 4 9 2 Additional Features qd eade OMA epe Eee dua EU 9 2 Conti guration 58U68 c S u uu 9 3 Case Sensitivity 9 3 9 4 Naming Conventions enr npe ron et ee ee ae 9 4 Examples 2 4 4 4 4
362. s to be retrieved Required Value Definition SNA destination name Specifies the SNA name of the remote system where the transfer is directed 1 to 8 characters Group name Specifies the name of a destination member defined in the Unicenter CA XCOM Data Transport Control Library This member can contain a single SNA LU name or TCP IP name or address or up to 16 SNA LU names 1 to 8 characters List name Specifies a list of SNA LU names and or TCP IP addresses 1 to 8 characters Login user name Specifies a user ID on the source computer whose access privileges are used to execute the file transfer 1 to 8 characters IP destination name Specifies the IP destination name of the remote system where the transfer is directed 1 to 63 characters nnn nnn nnn nnn Specifies the IP address of the remote system where the transfer is directed The contents of the Remote System Identification field reflect the choices made in the Primary Option Menu screen The first item in the field identifies one of the Unicenter CA XCOM Data Transport destination types that is the first item is one of the expressions IP Name Addr SNA LU Name XCOM Group Name XCOM List Name or Login User Name depending on what was entered as the destination type on the Primary Option Menu screen If the first item in the field is IP Name Addr another field IP Port appears to the right on the same line The second item in the Remote System Id
363. sage is displayed in the upper right corner of a panel You can display the long form of the message on line 3 of a panel by entering the ISPF HELP command or pressing the Help key usually PF1 or PF13 The messages are self explanatory The Batch Interface This chapter describes how Unicenter CA XCOM Data Transport is invoked from a batch job to execute a file transfer local and remote z OS users may send and retrieve data files between z OS and other z OS or non z OS systems using the Unicenter CA XCOM Data Transport Batch Interface In addition all local z OS users may use the Batch Interface to send jobs and reports for processing to remote systems The Batch Interface 3 1 Special Features Special Features The Batch Interface supports all Unicenter CA XCOM Data Transport features including the following special features Third Party Processing Third party processing involves a situation where a computer system is used to arrange for a second computer system to send a file job or report to a third computer system at a specified future time if not immediately For important information about third party processing see the description of the parameters STCAPPL in the section PARM Parameters LPASS and LUSER in the section General SYSINO1 Parameters Broadcast Distributions A file can be sent to multiple targets a broadcast list at the same time For important information on broadcast distributions see th
364. sages An LU is a set of rules and responsibilities LUs can be either dependent or independent and each LU type is associated with a protocol for example LU 0 LU 6 2 The LU provides a connection into SNA for the end user which may either be an individual or a transaction program for example Unicenter CA XCOM Data Transport It allows end users to communicate with each other and with other network addressable units NAUs in the network Logical and Physical Network Components An SNA network is divided into physical and logical components The physical network consists of the following m Actual processors called nodes m Data links between the nodes About SNA Logical Units 1 Parts of a Network Sessions PCIDs A 2 User Guide The logical network consists of a set of software components called network addressable units NAUs that include the following m Logical units LUs m Physical units PUs m System services control points SSCPs The logical connection between two NAUs is a session Although several types of sessions exist the end user is aware of only one type that is LU to LU Sessions are established when one LU sends another LU an SNA request known as a BIND Each session has its own PCID A procedure correlation identifier PCID is an eight byte field placed in the BIND UNBIND and other SNA requests to help an LU distinguish one session from another It is required when you are running parallel
365. se eek tor PUR DE ROC SD SET SY RG 9 16 Remotely Initiated Send Requests 9 16 IWIN ess Annee knee 9 17 Naming amp ade 9 17 Types Of Piles S pported conu date oe metres teme rettet ied see oe S 9 17 En ate nte 9 17 Trusted ACCESS cnet aed eoe S E EE ERE E tete E Si EEEN ERE aE 9 18 9 18 Naming eee pane E 9 18 22 2 2 222 eee eee eee 9 19 DC D s as Sans a asen a ae a A te A Fateh 9 19 IRGS ACTON MM 9 19 l 9 20 VSAM Naming ConventiOns oco oc doce ten occa best eet ee 9 20 SAM Naming Conventions 9 21 TAPE Naming ConvehtiOns acerbe dale tobe eee Meeps 9 23 VSAM Managed SAM Naming 1 9 24 ee sma ku aa saa ss Pa 9 25 Types of Biles Supported 25220
366. sessions A PCID is also known as a session identifier SID in VTAM displays For each session VTAM prompts you to note the primary or secondary node and displays the Session ID SID in hex This SID is the PCID If a trace of the BIND is taken the PCID vector is towards the end The following VI AM operator command lists all sessions generated for that LU D NET ID lt Zuname E Logical Units IBM s Strategic LU LU Types Logical Units This section describes the different LU types LU 6 2 is the only LU type that is crucial to IBM s long term strategy The 3270 data stream will be moved on top of LU 6 2 and none of the other LU types are strategic for example they are not considered in IBM s long term plans IBM classifies LUs into roughly seven different types LU 6 2 is a subset of LU 6 The products that support each of these LU types will continue to be supported in future years and the 3270 data stream will also be preserved but not in its current form The following table lists all of the LU types that are in use today to differing degrees LU Type 0 6 1 Definition A roll your own protocol which eliminates standardization beyond layers of SNA This was commonly used in the late 1970s before the advent of LU 6 2 The protocol used as early as the 1960s by remote job entry devices such as the 3770 RJE terminal Designed for use with printers and card readers this protocol is most typically us
367. sfer Display Select CA XCOM Server XCSDSL Select Transfers gt Inactive Active Completed Limit display to transfers for the following Requesting User ID gt 01 Remote System TCP IP Y N gt Remote System ID gt Request Number gt Transfer ID Date Range Start YYYYMMDD End YYYYMMDD Maximum Entries PFK 1 Help 3 End C 2002 COMPUTER ASSOCIATES INC COMMAND gt 1 1 F2 SPLIT F3 End F4 RETURN F5 RFIND 6 F7 UP F8 DOWN F9 SWAP FlO0 Language 11 1 F12 Alloc Selecting a Display Option To display a list of file transfers from one or more categories Inactive Active Completed enter a non blank character in front of each category that you wish to obtain information about and press ENTER For example to display a list of all file transfers that are yet to start and those that are already underway place a non blank character in front of the file transfer categories Inactive and Active For more information see the XCOM Transfer Request Display screen in this chapter The transfers appearing in the list include locally initiated remotely initiated indirect and third party initiated file transfers 2 108 User Guide Unicenter CA XCOM Data Transport Operator Control Modifying the Filtering Options Parameter Fields You can filter the information displayed further by entering values in the other fields on this screen For example if you want the stat
368. slow down file transfers making it too long will increase the risk of data loss It is recommended that the Checkpoint Count be set to at least 1000 On Token Ring Ethernet and other high speed networks the Checkpoint Count should be set to the highest allowable value If the receiving system is z OS or VSE the Checkpoint Count should be a multiple of the blocking factor For example if the DCB attributes are RECFM FB LRECL 80 BLKSIZE 8000 the Checkpoint Count should be a multiple of 100 The Menu Interface TSO ISPF Panels 2 87 Receive File From Another System Screen Compression Mode 2 88 User Guide Specifies whether Unicenter CA XCOM Data Transport compresses the data being transferred and decompresses it on the receiving system Compressing the data decreases the transmission time on lower speed lines Value Definition YES Provides Run Length Encoding RLE for blanks and binary zeros only NO No data compression RLE Provides complete Run Length Encoding for all characters COMPACT Provides full RLE as in RLE above plus a byte compaction scheme that is suitable for uppercase English text COMPACTL Same as COMPACT above only the compaction scheme is most beneficial for lowercase English text LZSMALL Lempel Ziv 77 compression with a small memory allocation scheme LZMEDIUM Lempel Ziv 77 compression with a medium memory allocation scheme LZLARGE Lempel Ziv 77 compression with a large memory allocation
369. splay Detailed File Transfer Display Information on a particular file transfer request is displayed on a screen similar to the one that follows To invoke the display for a transfer enter S or D next to it in the 5 column of the Unicenter CA XCOM Data Transport Transfer Request Display CA XCOM RECEIVE FILE 0 123456 QUEUED THURSDAY OCT 14 2004 14 59 35 COMMAND INPUT gt CA XCOM Server XCOMRTL Sched Start Time THURSDAY OCT 14 2004 14 59 35 Transfer ID USERTEST End Time THURSDAY OCT 14 2004 23 11 53 Last Action NOT USED Status FILE ERROR Priority Sel 016 Exec 016 Compress Mode YES Trans Time Secs 29538 Compress Factr 06 6 Transfrd Records 32 246 874 Bytes 3 224 687 500 Bytes Sec 109170 Compress Bytes 3 289 181 250 Last Ms XCOMMO221E DATASET OUT OF SPACE SENDING SYSTEM INFORMATION System ID 123 123 123 123 User ID USERO1 Notify ID N A Unit Volume File Type File Name C USERS ABC 6GB RECEIVING SYSTEM INFORMATION System ID LOCAL User ID USERO2 Domain Notify ID N A Unit Volume SAMP Option CREATE File Name 05 02 5 If the transfer is in progress the cumulative number of records transferred and elapsed time are displayed If the transfer request is completed the total number of records transferred and elapsed time and the date and time of completion are displayed To refresh these fields for an active transfer press ENTER The display consists of three s
370. sport by parameters passed through the application program These can be one time values for individual file transfers or they can be installation wide defaults implemented automatically The Unicenter CA XCOM Data Transport routine XCOMJOB runs as a called program and is the same program used in the Unicenter CA XCOM Data Transport Batch Interface see the chapter The Batch Interface The program that calls XCOMJOB must pass the equivalent of the EXEC PARM values and must prime the local and SYSINOI data sets The instructions for coding the PARM values and the SYSINO1 parameters are identical to those for the Unicenter CA XCOM Data Transport Batch Interface and are fully described in the chapter Batch Interface Note TYPE EXECUTE and TYPE SCHEDULE are supported with the APIs WARNING Calls to Unicenter CA XCOM Data Transport as a subprogram should be dynamic using the LOAD or LINK macro Do not try to link edit any of the Unicenter XCOM Data Transport modules to your program Allocating the Local Data Set and Parameter Files Allocating the Local Data Set and Parameter Files This section describes how to allocate your local data set and parameter files Define Two Unicenter CA XCOM Data Transport Files To call Unicenter CA XCOM Data Transport as a subprogram you must define two Unicenter CA XCOM Data Transport files in the job step executing your application File Description The file identifying the local Thi
371. sport down using console command for example FXCOM STOP Stage Action 1 Copies the Unicenter CA XCOM Data Transport history file to a temporary sequential dataset using the IDCAMS REPRO command 2 Executes the XCOMUTIL program to purge records from the passed sequential data set that are older than x days and passes the selected records to stage 4 below 3 If XCOMUTIL purged all records from the History File generates a new binary zero seed record for the history file using the MVS utility IEBDG 4 Calls IDCAMS to do the following a Delete the old history file cluster alternate indices and paths b Redefine the base cluster e Copy the seed and the selected records back into the base cluster d Redefine and rebuild the alternate indices and paths After finishing the above purge restart Unicenter CA XCOM Data Transport with another command for example START XCOM B 6 User Guide Appendix Sample Files This appendix contains illustrations of some of the sample files supplied on the Unicenter CA XCOM Data Transport for z OS distribution tape These are supplied for reference only Important In cases where the printed examples differ from what is provided on the distribution tape the tape is more current Sample JCL VSAM Request Queue Member DEFRRDS The following is copy of the sample JCL VSAM Request Queue CALCINBOSAM DEFRRDS found on the distribution tape This JCL builds active and pen
372. st The maximum possible wait is one second less than 100 hours Value Definition 000000 to 995959 Specifies how long Unicenter CA XCOM Data Transport should wait after a transfer request before determining and reporting the status of a transfer request Notes Only valid for TYPE INQUIRE transfers Default The value specified in Unicenter CA XCOM Data Transport Default Options Table IPNAME Identifies the IP address of the remote system for a TCP IP transfer Value Definition 1 to 63 alphanumeric Specifies the address of the remote IP node with a name characters that must be defined or known to the domain name server nnn nnn nnn nnn Specifies the address of the remote IP node with a number in dotted decimal notation The Batch Interface 3 39 SYSINO1 Parameters IPPORT JPNCNTL 3 40 User Guide Identifies the IP port of the remote system for a TCP IP transfer Value Definition 1 to 65535 Specifies a number indicating the IP port of the remote system Default If this parameter is not specified the value of IPPORT parameter defined in the Unicenter CA XCOM Doata Transport Default Options Table is used When GROUP or LIST is used the value for IPPORT is determined by either the destination member or the default table Indicates whether the header file contains Katakana characters Value Definition KorKATAKANA The control information header fields being transferred contains Katakana character
373. st To reduce system overhead specify PSOW AIT YES if there are more than a 100 nodes in the Destination Table Otherwise specify NO For a description of the PPOWAIT parameter see the Unicenter CA XCOM Data Transport for z OS Administrator Guide JES2 Considerations When you are using JES2 you need to use valid destination names as described in this section Valid Destination Names JES2 can support thousands of distinct user destinations Destination names defined JES2PARM be changed to destination names defined in the Unicenter CA XCOM Data Transport Destination Table For example U123 might be equated to Boston U007 to VAXNY and U2001 to SYSAS400 through JES DESTID statements in JES2 DESTID DEST U123 DESTID NAME SYSAS400 DEST U2001 DESTID NAME VAXNY DEST U007 The DESTID NAME must be a 1 to 8 character alphanumeric entry For more information see your JES2 Systems Programming Manual JES3 Considerations When you are using JES3 you need to use valid destination names as described in this section Valid Destination Names 5 10 User Guide There is no limit on the number of distinct destination names JES3 can support JES3 also allows destination names to be specified either directly or generically Unlike JES2 JES3 provides no default destinations Destinations are defined using the RJPWS macro When RJPWS is used the CONSOLE statement is also required JES3 Consider
374. strictions on size for the individual parts of the path The following table describes the parts of a UNIX path Part Description slash root directory when it is in the first position otherwise the slash separates directories and file names in the path directory directory that contains the file You can specify more than one directory in a path filename The name of the UNIX file Types of Files Supported Unicenter CA XCOM Data Transport for UNIX supports standard UNIX file types Restriction Unicenter CA XCOM Data Transport does not support library transfers to UNIX systems Remote System Information 9 17 VM Trusted Access VM Unicenter CA XCOM Data Transport for all UNIX platforms running Version 3 0 or higher supports Trusted Access To use the Trusted Access feature when transferring to UNIX based platforms note the following m The USEROVR and USERPO default table parameters for Unicenter CA XCOM Data Transport for z OS must be set to YES m Specify USERID and no passwords in the parameters for the transfer m The user ID must be configured for Trusted Access on the UNIX partner For more information see the Unicenter CA XCOM Data Transport for UNIX documentation This section contains information about important aspects of the VM operating system Naming Conventions 9 18 User Guide Use the following format to name VM files under the CMS operating system filename filetype
375. system Value Definition YES Tells Unicenter CA XCOM Data Transport to transfer the file as a PDSE program library This parameter is the equivalent to PROGLIB YES in SYSINOI NO Tells Unicenter CA XCOM Data Transport that the file does not involve a PDSE program library and should be handled as a regular file transfer Notes There is no default value for this parameter Unless YES is specified the file is handled as a regular transfer The Menu Interface TSO ISPF Panels 2 23 Send MVS File To Another System Screen Create Add Replace 2 24 User Guide Informs Unicenter CA XCOM Data Transport how to handle the file that is receiving the transferred data on the remote system This is the file whose name appears in the Remote File Name field Value C reate A dd R eplace Notes Definition Unicenter CA XCOM Data Transport attempts to create allocate a new file on the remote system For information concerning the provision of additional allocation parameters for this new file see File Allocation Information Screen in this chapter Unicenter CA XCOM Data Transport adds the records being transferred to the end of an existing file on the remote system For an indexed file the keys must not match those in the file on the remote system or Unicenter CA XCOM Data Transport will terminate the transfer with an error Unicenter CA XCOM Data Transport replaces the contents of a file on the remote system with the d
376. system to other systems Advantages of Using the Process SYSOUT Interface The Process SYSOUT Interface allows passive use of Unicenter CA XCOM Data Transport No Unicenter CA XCOM Data Transport commands or Unicenter CA XCOM Data Transport JCL procedures are necessary User programs IBM utility programs such as IEBGENER and common TSO commands such as PRINTOFF VPSPRINT and DSPRINT can invoke Unicenter CA XCOM Data Transport Process SYSOUT files can contain logical records up to 4K bytes in length This allows Unicenter CA XCOM Data Transport to extract very large records from the spool Indirect store and forward file transfers also support logical record lengths up to 4K Note The 4K limit is a restriction of JES2 and JES3 The Remote Spooling Feature Process SYSOUT 5 1 Basics of JES Spool Use Process 5 2 User Guide To summarize the Process SYSOUT Interface offers the following advantages m Handles SYSOUT record lengths up to 4K m Transfers different types of data including binary characters Handles all of the following Files only with indirect transfers Jobs to be executed on the remote system only with indirect transfers Reports to be printed on the remote system m Allows data to be queued to remote destinations via the JES spool even when the Unicenter CA XCOM Data Transport server is temporarily down m Allows Unicenter CA XCOM Data Transport to act as a replacement for the Network J
377. t name If the remote system is a Windows machine specify the full pathname If the remote system is an AS 400 specify the qualified filename If the remote system is a DEC VAX computer specify the VMS filename If the remote system is a UNIX system specify the fully qualified filename including path information 3 56 User Guide FILEOPT SYSINO1 Parameters Indicates how the transferred file is managed by the receiving computer Value Definition REPLACE Replaces the file on the receiving computer ADD CREATE Notes If the VSAM file isa This is replaced KSDS cluster Records with matching and non matching keys ESDS cluster Nothing All records are added to the end of the data set since a non reusable ESDS can only be replaced by deleting and redefining the cluster Use CREATE to replace reusable VSAM clusters RRDS cluster Nothing this is an invalid choice Note If sending a new member to a pre existing PDS specify REPLACE Adds the records of the transferred file to the end of an existing sequential file or inserts them into an indexed file if they do not already exist there If the records do already exist there Unicenter CA XCOM Data Transport aborts the transfer Note You cannot add to an existing PDS member Creates the transferred file on the destination system as a sequential file This option should also be used when VSAM clusters with the REUSE option are to be reused If the tr
378. t request The Batch Interface 3 45 SYSINO1 Parameters Multiple SNA and TCP IP transfers be intermixed within the same SYSINO1 stream For information about TYPE EXECUTE transfers see the discussion of the CONTINUE parameter for XCOMJOB PARM NOTIFY Tells Unicenter CA XCOM Data Transport whom to notify on the local system when the file transfer is complete This parameter is used in conjunction with NOTIFYNAME See also RNOTIFY Value Definition LOG Requests that the main console operator on this computer be notified user id Identifies the 5 user who is sent a broadcast message when the file transfer completes Any value except LOG is interpreted by Unicenter CA XCOM Data Transport as a TSO user ID on this system If this user ID is not logged on when the transfer is completed the message is displayed the next time the user logs on Note Do not use NOTIFYNAME or RNOTIFYNAME operands for TSO users CICS Causes Unicenter CA XCOM Data Transport to begin an LU 6 2 process to CICS when the file transfer concludes See NOTIFYNAME ROSCOE Sends notification messages to users of Computer Associates Advantage CA Roscoe timesharing product when a file transfer begins ends or fails See NOTIFYNAME ALL If the remote computer is a VAX Unicenter CA XCOM Data Transport can send notification to the electronic mailboxes of DEC ALL in 1 users See NOTIFYNAME Notes If either NOTIFY CICS NOTIFY ROSCOE
379. t transfers 3 79 command security overview 8 1 compatibility with ISPF 2 3 completed transfers B 2 user exit D 2 COMPLT status field 2 118 COMPNEG PARM parameter 3 10 compound destinations 5 8 compress data Detailed File Transfer screen 2 121 Receive File From Another System screen 2 89 Send File screen 2 27 Send Report screen 2 58 Submit Job screen 2 73 COMPRESS 5 01 parameter 3 33 compression 3 10 mode Detailed File Transfer screen 2 121 types 3 33 concurrent transfers 3 45 console commands See MODIFY commands console routing codes 6 16 CONTINUE PARM parameter 3 11 control block dump 6 21 control fields 2 117 Index 2 User Guide control library enable 6 23 CONTROL SYSINO1 parameter 3 63 COPIES See COPY copies Send Report screen 2 54 COPY SYSINO1 parameter 3 63 COPYCSD sample JCL C 37 create remote file 2 23 2 86 create add replace remote file Send File screen 2 20 D Data Class parameter 2 45 data compression Receive File From Another System screen 2 89 Send File screen 2 27 Send Report screen 2 58 Submit Job screen 2 73 data set entry sequenced 7 6 key sequenced 7 6 multivolume 7 7 name Receive File screen 2 43 partitioned 7 1 relative record 7 6 TSO 5 7 DATACLAS SYSINOT parameter 3 34 Dataset Name Type parameter 2 46 date alter priority 6 8 range operator control parameter 2 113 start 2 103 LOCATE command 2 116 s
380. table describes the parts of a SAM file name Part Description file id The name that identifies this data set in the VTOC of the specific DASD volume This is the file id you specify on the DLBL JCL statement Range 1 to 44 characters Note Do not enclose it in quotes S Indicates that this is a SAM file unit The physical device address as defined by the CUU parameter on the ASSGN JCL statement It identifies the disk drive on which this file resides This parameter can be omitted if the UNIT or VOL parameters are specified or if a DASD manager is in use location Optional for output files The starting location of the file on the disk as defined on the EXTENT JCL statement If a DASD manager is in use specify a value of 1 size Optional for output files Indicates how much space this data set will use as defined on the EXTENT JCL statement For CKD devices this is the number of tracks For FBA devices this is the number of blocks Remote System Information 9 21 VSE 9 22 User Guide Part override Description Optional for output files The following override parameters may be specified The equivalent DFLTAB option is included to describe each override parameter 1 DMYES to force DASDM YES for this file 2 DMNO to force DASDME NO for this file 3 DMEPIC to force DADSM EPIC for this file Note If you are running with a DASD manager the DASD manager s STRTTRK or Trigger value would be placed in
381. tatus 2 118 unprotected field 2 117 DATE attribute label 2 116 XCOMUTIL parameter B 4 DCB information examples 3 74 parameters See also SYSINO1 parameters BLKSIZE 3 72 LRECL 3 73 3 73 DD statements 3 5 LCLDSOI 4 2 deactivate trace with command line 6 30 6 31 deactivation parameters trace 6 30 DEC 9 8 DECnet APPC A 5 default menu interface 2 2 Default Options Table sample C 15 default parameters modifying dynamically AGE 6 16 CATALOG 6 16 CLASS 6 16 DIR 6 16 DUMPCL 6 16 EDESC 6 16 EROUT 6 16 ERRINTV 6 16 IDESC 6 16 IROUT 6 16 JESINTV 6 17 LOG 6 17 LOGCL 6 17 LOGDEST 6 17 MAXLOC 6 17 MAXREM 6 17 MAXTASK 6 17 PRI 6 17 PSOUNIT 6 17 PSOVOL 6 17 REMAGE 6 17 SEC 6 17 SMF 6 17 SMENUM 6 17 TCPSESS 6 17 UNIT 6 17 USERD 6 17 VOL 6 17 DEFDFLT sample JCL C 35 DEFHIST sample JCL C 3 DEFINQ sample JCL C 10 DEFQSAM sample JCL C 9 DEFRRDS sample JCL C 1 DELETE MODIFY command 6 15 DEN SYSINO1 parameter 3 67 DEST SYSINO1 parameter 3 64 DESTID JES2 destination statement 5 10 destination name JES 5 10 DFLT MODIFY command 6 16 DFLTAB PARM parameter 3 11 DIR system parameter 6 16 direct access data set support 7 7 DISABLE MODIFY command 6 18 DISP SYSINO1 parameter 3 64 DISPALG PARM parameter 3 12 display current values with command line 6 27 DISPLAY MODIFY command 6 20 DOMAIN PARM parameter 3 12 Receive File Fr
382. te This field which is used in conjunction with the Save SYSINO1 in DS Name field allows you to create a SYSINOI file for later use with the Batch Interface Default N MVS Send Functions Menu MVS Send Functions Menu The MVS Send Functions screen shown below is used to select one of the three types of outbound transmissions made with Unicenter CA XCOM Data Transport Data is transmitted to a remote system in the form of a file report or job The other fields displayed on the screen reflect the entries made on the previous Primary Option Menu and may be overridden on this screen 04 10 26 Unicenter CA XCOM r11 5 00 TURKIO1 MVS Send Functions 1 2 x 3 Remote System Identification IP Name or Address or SNA LU Name or XCOM Group Name or XCOM List or Login User Name Queue for Execution Y N Y APPLID of the CA XCOM Server PFK 1 Help 3 End OPTION gt 1 1 1 F2 SPLIT F7 UP F8 DOWN F3 End F9 SWAP Send Functions Menu Options F1l0 Language 11 1 Send Files to Another System Send Reports to Another System Submit Jobs to Another System Execute immediately C 2002 COMPUTER ASSOCIATES INC F4 RETURN F5 RFIND 6 F12 Alloc The options for the MVS Send Functions screen are described in the following table Option 1 Send Files to Another System 2 Send Reports to Another System 3 Submit Jobs to Another System D
383. tem catalog Indicates the unit on the remote system from which the file is to be retrieved Value Definition XXXXXXXX Specifies the unit name on the remote system from which the file is to be retrieved This value can be up to eight alphanumeric characters Default The unit determined by the remote system catalog Receive File From Another System Screen Local System Information User ID The Local System Information fields of the Send MVS File To Another System screen pertain to the local or transfer initiating Unicenter CA XCOM Data Transport system Identifies the user ID under whose set of resource access privileges this file transfer is to execute on the source transfer initiating computer Value Definition Up to 8 Specifies the user ID under whose set of resource access characters privileges this file transfer is to execute on the source computer Notes This information is primarily used for third party processing For example a Unicenter CA XCOM Data Transport node in New York could request that a Unicenter CA XCOM Data Transport node in Los Angeles send a file to a Unicenter CA XCOM Data Transport node in Chicago To use this feature all systems must be identified to VTAM and running Unicenter CA XCOM Data Transport Version 2 or higher For conventional that is non third party file transfers use this parameter to identify the user that initiated the transfer This is useful when performing operator tracking and
384. terface TSO ISPF Panels 2 5 The Primary Option Menu Primary Processing Parameters The primary processing parameters for the Primary Option Menu are described below Remote System Identification IP Dest Port 2 6 User Guide Identifies the partner system involved in a Unicenter CA XCOM Data Transport transfer The terms in which the partner systems can be identified are described below Specifies the name or address of the TCP IP system or node with which transfer is to take place Value Definition Xi X63 Specifies the name of the remote TCP IP system involved in a transfer This name can contain up to 63 alphanumeric characters and it must be one that has been defined to the domain name server nnn nnn nnn nnn Specifies the address of the remote TCP IP system in dotted decimal notation Notes This parameter is mutually exclusive with SNA LU Name XCOM Group Name Login User Name and XCOM List Name one of the five must be specified for each file transfer request Specifies the number of the IP port where Unicenter CA XCOM Data Transport listens at the remote system Note This field is displayed on subsequent screens only if an IP name or address is specified in the Remote System Identification field Value Definition 1 to 65535 Identifies the IP port monitored listened to by Unicenter CA XCOM Data Transport at the remote system SSL CONFIG SSL The Primary Option Menu Notes If this fiel
385. ters Tells Unicenter CA XCOM Data Transport to use the pooled LU feature to allow for multi threading of transfers to nodes that support multiple logical units but not parallel sessions For TCP IP transfers use GROUP to specify an alias Value Definition xxxxxxxx Specifies the name of a group of LUs defined in the Unicenter CA XCOM Data Transport control library CAI CINBOCTL The name can contain up to eight characters The first character must be alphabetic while the rest can be any combination of alphanumeric or national characters Notes GROUP LIST USER and LU are mutually exclusive parameters Only one of them may be coded When GROUP or LIST is used the value for IPPORT is determined by either the destination member or the default table The group must be predefined in the Unicenter CA XCOM Data Transport control library CAI CINBOCTL When the transfer process begins Unicenter CA XCOM Data Transport tries transferring to the first LU in the group If that attempt fails the second LU is tried If that transfer attempt fails the third LU is tried and so on However as soon as Unicenter CA XCOM Data Transport finds an LU that is available for the partner node it transfers the data to that LU and stops making any further transfer attempts Group processing is supported for TCP IP transfers but only for a single IP address In this way an alias may be defined within Unicenter CA XCOM Data Transport for an IP a
386. ters at Entry The following registers are available at entry Register Description RO Undefined R1 Address of SMFDSECT R2 to R12 Undefined R13 Address of register save area R14 Return address R15 Entry point address D 2 User Guide Registers at Exit Valid Return Code Sample Program User Exit 1 The following registers are available at exit Register Description RO to R14 Undefined R15 Return code The only valid return code is 0 for a normal return The following is a sample program using this exit CAI CINBOSAM XCOMEX01 Note Exit 1 is invoked only when the transfer is scheduled and run via the Unicenter CA XCOM Data Transport 2 server It is not invoked when XCOMJOB TYPE EXECUTE is used User Exits D 3 User Exit 2 User Exit 2 Purpose This exit allows the execution of a user developed exit routine that extracts additional information from JES2 control blocks information not extracted by the XCOMPSOI module Module Name and Entry Point The module name and entry point for this exit is XCOMEX02 How to Enable Specify EXITO2 YES in the Default Options Table to enable this exit Calling Module The module XCOMPSOI calls this exit Entry Method This exit is a branch entry Required DSECT PSODSECT is the required DSECT Addressing Mode at Entry The addressing mode at entry is 31 Registers at Entry The following registers are available at entry Register Description RO Undefined R1 Ad
387. th the following data 00601 CURRENT RELEASE IS r m GENERATION LEVEL where r m indicates the release and modification level and yymm year month indicates the maintenance generation level Using the Unicenter CA XCOM Data Transport MODIFY Commands Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name READ XCOM applsec V ERSION destname ownername The variable represents the following value m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination involved in the transfer m ownername the user ID under whose security authorization the transfer is performed XRSHOW Command Format Operands For XCOMPLEX Admin Server only Displays remotely initiated transfers for all XCOMPLEX Worker Servers connected to the XCOMPLEX Admin Server F XCOM XRSHOW nnnnnn The following is the operand for the XRSHOW command Operand Description nunnan Specifies the number 0 to 999999 of the transfer request about which information is to be displayed Operation and Control 6 49 Using the Unicenter CA XCOM Data Transport MODIFY Commands Notes If you enter XRSHOW without an operand the resulting display lists remotely initiated file transfer requests If you select an individual requ
388. that attempt fails the second LU is tried If that transfer attempt fails the third LU is tried and so on However as soon as Unicenter CA XCOM Data Transport finds an LU that is available for the partner node it transfers the data to that LU and stops making any further transfer attempts Group processing is supported for TCP IP transfers but only for a single IP address In this way an alias may be defined within Unicenter CA XCOM Data Transport for an IP address When GROUP or LIST is used the value for IPPORT is determined by either the destination member or the default table Session establishment is subject to a time out limit defined on the TIMEOUT parameter See the description of this parameter later in this section The Batch Interface 3 15 PARM Parameters IDESC 3 16 User Guide Specifies the 16 bits coded in hexadecimal of a z OS message descriptor code Value Descriptor Definition hexadecimal Codes 8000 1 System failure 4000 2 Immediate action required 2000 3 Eventual action required 1000 4 System status 0800 5 Immediate command response 0400 6 Job status 0200 7 Application program processor 0100 8 Out of line message 0080 9 Status display 0040 10 Dynamic status display 0020 11 Critical eventual action required 0010 12 Important information message 13 Reserved for future use Notes The codes are selected by the bit configuration where bit 0 corresponds to descriptor code 1 bit 1
389. that this is a file Note If you enter a transfer request from a platform that has not yet implemented the extended tape processing parameters or menu interface fields for controlling tape processing to a Unicenter CA XCOM Data Transport VSE server you must use the T option You are restricted to standard label tape processing unit The physical device address as defined by the CUU parameter on the ASSGN JCL statement If you are using TAPEM YES EPIC Unicenter CA XCOM Data Transport ignores any units coded and the tape manager does the tape AVR and assignment If you are not using the tape manager the primary assignment is made to the first unit Unicenter CA XCOM Data Transport finds Other units found are assigned as temporary alternates This parameter can be omitted if you prefer to use the UNIT parameter to specify a unit or two units primary and alternate This parameter can be used in conjunction with the UNIT parameter to specify a primary unit and up to four alternate units that will be assigned Unicenter CA XCOM Data Transport prior to open Units specified on the statement containing the file id will be assigned before units specified on the UNIT parameter The unit parameter is ignored because tape processing is only supported when you have a tape manager on your VSE system Remote System Information 9 23 VSE Part override Description Optional for output files The following override parameters ma
390. the RRDDSECT macro while the transfer is pending or active The RRDSUSER field is defined by HDRDSECT within RRDDSECT Value Definition 1 to 10 bytes Specifies up to 10 bytes of data available to user exits during a file transfer Remote System Information User ID The Remote System Information parameter fields of the Submit Job screen are described in the following Identifies the user ID under whose set of resource access privileges the transfer is to execute on the remote system Make this a user ID known to the security system resident on the remote system Value Definition XXXXXXXXXXXX Specifies up to 12 alphanumeric characters The Menu Interface TSO ISPF Panels 2 75 Submit Job To Another System Screen Password 2 76 User Guide Notes For a third party file transfer this parameter provides the user ID for the target remote system For more information about the Unicenter CA XCOM Data Transport security interface see the chapter Overview of Unicenter CA XCOM Data Transport Security To send a blank parameter value to the remote system enter inserting at least one blank space between the quotation marks Do this when the remote system supplies its own default value for the user ID under whose access privileges the file transfer is to execute on the remote system Note Many systems do not perform security checking on reports If this is the case skip this and the Remote Password parameter De
391. the location field DASD manager pools should be indicated by putting the pool name in the Volume parameter For EPIC VSE users you may omit m The location if you want EPIC to default to its STRTTRK value m The size if you want EPIC to default to its DEFEXT value a The Volume information if you want EPIC to default to its DEFPOL value For Brightstor CA Dynam T users who want to access Dynam catalog controlled files included GDG data sets no extent information should be entered No cuu location size or override information and no Volume or Unit parameters for the files you are referencing VSE TAPE Naming Conventions Use the following format to name a TAPE file file id T unit unit unzt override The following table describes the parts of a TAPE file name Part Description file id The name that identifies this data set in the tape manager catalog or in the HDR1 label on the tape This is the file id you specify on the TLBL JCL statement Range 1 to 44 characters Note When the file id contains imbedded spaces or commas it should be enclosed in quotes Note IBM only supports a 17 character file id in a tape header label If you have a tape manager 44 character tape file ids may be supported Unicenter CA XCOM Data Transport does not validate your file id but takes whatever you put on the statement and passes it to IBM s OPEN routine or to your tape manager as you have entered it T Indicates
392. the one chosen for the initial SYSINO1 When using XTC to submit multiple jobs or job steps with the same XTCNET and XTCJOB names submit directly to the CA XCOM server This ensures that they go to the same CA XCOM SERVER At the end of each XTC run ensure that there are no XTC transfers left in HOLD status Use the Unicenter CA XCOM Data Transport DELETE or RELEASE operator commands to do this For more information see the chapter Operation and Control Tip Before resubmitting an XTC transfer job go into the appropriate servers and use the Unicenter CA XCOM Data Transport SHOW command to check for any left over XTC transfers Use the above procedure to clean up any transfers in HOLD status XCOMJOB Return Codes The following table lists the return codes that an XCOMJOB may return Return Code Description Valid XCOMJOB Type 0 Successfully scheduled or executed types transfer all transfers completed successfully 1 Partially successful at least one TYPE EXECUTE transfer worked successfully TYPE SCHEDULE 4 XCOMINO file is empty TYPE INQUIRE 8 ACB not open TYPE EXECUTE TYPE SCHEDULE Unable to access the XCOMINO file TYPE INQUIRE 9 Session not established All types 10 A TIMEOUT occurred TYPE EXECUTE TYPE SCHEDULE 12 A file error occurred TYPE EXECUTE TYPE SCHEDULE 3 82 User Guide SYSINO1 Parameters Return Code Description Valid XCOMJOB Type 16 A logic error occurred TYPE EXECUTE TYPE SCHEDULE
393. the system master catalog In short this means that the system will be able to locate the file you specify by name only With the rare occurrence of an uncataloged file you need to specify the volume and unit information for the device that holds the file 9 4 User Guide Examples z OS The following are examples of valid z OS data set names SYS1 VTAMLST C54684 UTILITY CNTL JOBCARD PROD PAYROLL SEPT90 TIMECARD DATA TESTDATA A DDD LOAD Types of Files Supported DCB Information Sequential files are the most common forms of data transferred Individual members of PDS files may also be sent as sequential files Entire PDS libraries or multiple selected members may be transferred between two z OS systems or to other systems running Unicenter CA XCOM Data Transport r11 PDSE and entire PDSE program libraries are supported in Unicenter CA XCOM Data Transport r11 PDSE program libraries do not support wildcarding All three types of VSAM files KSDS ESDS and RRDS may be transferred between z OS systems These VSAM files must be pre allocated or they may be sent to non z OS systems as sequential files ISAM BDAM direct access IMS FDR and DFDSS data sets are not directly supported but they can be put into a sequential format using native utilities prior to transmission The file characteristics for z OS must be predefined when creating a new file Collectively the following characteristics are known as Data Cont
394. tion 1 to 999 Specifies a number of days that the request can remain on the Unicenter CA XCOM Data Transport queue before being purged Notes The Unicenter CA XCOM Data Transport queue includes file transfer requests with future start dates Hold status or Suspended status Automatic queue purging is performed by Unicenter CA XCOM Data Transport each time the Unicenter CA XCOM Data Transport server comes up and daily at midnight Aging is relative to the scheduled start date of the file transfer Default As specified for the AGE parameter of the Unicenter CA XCOM Data Transport Default Options Table The Menu Interface TSO ISPF Panels 2 105 Member Selection List Member Selection List Specifying the name of a partitioned data set without a member name in the Local File Name field on any of the file transfer screens Send MVS File To Another System Submit Job To Another System Send Report To Another System or Receive File From Another System automatically brings up a Member Selection List screen that follows which lists the members of that partitioned data set This list allows one or more of the members in the data set to be selected for transfer to or from the remote system MEMBERLIST DA1SZ95 XCOM R11 SAMPLIB ROW 00001 OF 00036 COMMAND gt SCROLL gt PAGE NAME Prompt SIZE CREATED CHANGED INDEX 42 03 03 20 03 03 20 APPLXCOM 76 03 03 20 03 03 20 ASM TBLS 56 03 03 20 03 03 23 2 DA1EG79 ASMACF 2U 44 03 03 20 03
395. to begin Value hhmm thhmm tmm Notes Definition Specifies the hour and minute of the day when the transfer is to begin in the 24 hour clock format The range of values for the hour hh is 00 24 The range of values for the minute mm is 00 59 For example to schedule a transfer to start at not before 2 p m specify 1400 Specifies the transfer start time in terms of a number of hours hh and minutes mm after the current hour and minute The range of values for the hour hh is 00 24 The range of values for the minute mm is 00 59 For example if the current time is 1200 noon then specifying 0340 as the transfer start time means that the transfer is to start 3 hours and 40 minutes after the current time that is at 3 40 p m or 1540 in the 24 hour clock format Specifies the transfer start time in terms of a certain number of minutes mm after the current minute The range of values for the minute mm is 00 59 For example if the current time is 1710 or 5 10 p m then specifying 20 as the transfer start time means that the transfer is to start 20 minutes from the current minute 10 that is at 5 30 p m or 1730 in the 24 hour clock format If no value or a sequence of spaces is entered in the Start Time field the start time defaults to the current time If a value is entered in the Start Time field all digit positions indicated by the format must be filled Thus neither 1 nor 01 is a
396. to descriptor code 2 These codes are assigned to messages ending with I For more information see the EDESC parameter Default 0200 IPNAME IPPORT PARM Parameters Identifies the IP address of the remote system for a TCP IP transfer Value Definition 1 to 63 Specifies the address of the remote IP node with a name alphanumeric which must be defined or known to the domain name characters server nnn nnn nnn nnn Specifies the address of the remote IP node with a number in dotted decimal notation Identifies the IP port of the remote system for a TCP IP transfer Value Definition 1 to 65535 Specifies a number indicating the TCP IP port used when IPPORT is omitted Default 8044 Notes This parameter must match the SERVPORT specification of the target server and normally should not be changed When GROUP or LIST is used the value for IPPORT is determined by either the destination member or the default table The Batch Interface 3 17 PARM Parameters IROUT 3 18 User Guide Specifies the sixteen bits coded in hexadecimal of a z OS console routing code Value Descriptor Definition hexadecimal Codes 8000 1 Master console action 4000 2 Master console information 2000 3 Tape pool 1000 4 Direct access pool 0800 5 Tape library 0400 6 Disk library 0200 7 Unit record pool 0100 8 Teleprocessing control 0080 9 System security 0040 10 System error maintenance 0020 11 Programmer inform
397. transfer request is being resubmitted Value Definition YES Start from the nearest checkpoint do not start from the beginning of the transfer NO Signals that the file transfer should be restarted from the beginning even if a checkpoint restart is feasible NO is the default Default NO RNOTIFY SYSINO1 Parameters Tells Unicenter CA XCOM Data Transport whom to notify on the remote system when the file transfer is complete This parameter is used in conjunction with RNOTIFYNAME See NOTIFY Value LOG user id CICS ROSCOE ALL Notes Definition Requests that the main operator on the remote computer be notified Identifies the TSO user who is sent a message when the file transfer completes Any value except LOG is interpreted by Unicenter CA XCOM Data Transport as a TSO user ID on this system If this user ID is not logged on when the transfer is completed the message is displayed the next time the user logs on Causes Unicenter CA XCOM Data Transport to begin LU 6 2 process to CICS when the file transfer concludes This is only used when the remote computer is z OS Sends notification messages to users of Computer Associates ROSCOE timesharing product when a file begins ends or fails See RNOTIFYNAME Sends notification to the electronic mailboxes of DEC ALL in 1 users if the remote system is a VAX See RNOTIFYNAME If RNOTIFY CICS RNOTIFY ROSCOE or RNOTIFY ALL is selected then
398. transferred after data compression was performed on the records Trans Time Secs Bytes Sec Compress Factor Last Ms The duration of the file transfer in seconds The rate in bytes per second at which the transfer was accomplished The percentage of compression that was accomplished by the Unicenter CA XCOM Data Transport data compression routines compressed bytes divided by transferred bytes The last message issued by Unicenter CA XCOM Data Transport regarding the transfer The Menu Interface TSO ISPF Panels 2 119 Menu Interface Messages Sending Receiving System Information The sending receiving sections display the parameters that were entered when the file transfer was submitted data set name system ID user ID and so on In addition the Sending System Information or the Receiving System Information line will be highlighted to indicate the system that initiated the file transfer If neither line is highlighted this was a third party transfer initiated by a system other than the two displayed here Menu Interface Messages 2 120 User Guide Unicenter CA XCOM Data Transport comes with a set of messages in standard ISPF PDF format to assist the Menu Interface user The complete list of these messages is found in CAI CINBOSML XCOMOO These messages alert the user to errors such as failing to specify a required parameter or entering an invalid parameter value or command The short form of the mes
399. ts LUs that link the physical units PUs and transaction programs TPs Each Unicenter CA XCOM Data Transport user should be assigned a unique LU name for gateway or workstation identification Each data record traveling across the line will contain LU 6 2 protocol information containing instructions for the remote system The physical level consists of physical unit PU nodes linked by a physical connection Unicenter CA XCOM Data Transport supports transfers between physically connected systems whether they are directly or indirectly connected PU Type 2 1 nodes can make a direct logical link even without a direct physical connection Transfers involving PU Type 2 0 nodes like VAX VMS can be made using the store and forward feature of Unicenter CA XCOM Data Transport Introduction 1 5 Network Levels in the SNA Model Network Level Diagram The diagram below shows the various network levels used to communicate with Unicenter CA XCOM Data Transport END Unicenter Unicenter USER CA XCOM CA XCOM LEVEL Data Transport Data Transport Physical Connection Benefits of LU 6 2 APPC 1 6 User Guide Unicenter CA XCOM Data Transport is built upon the LU 6 2 protocol LU 6 2 is also known as Advanced Program to Program Communications APPC and is IBM s most powerful enhancement to the Systems Network Architecture SNA suite of communications protocols Network Levels in the SNA Model Improved Throughput Whe
400. tted if no member name is specified When transferring to another z OS system use generic specifications for the source file only not the destination file For example with a Receive File transfer on z OS you could use a generic specification for the Remote File Name but not for the Local File Name Wildcards in the z OS destination data sets are ignored Generation Data Groups If the destination is another Unicenter CA XCOM Data Transport r11 partner wildcard characters are allowed in the destination file name depending on the system to which the transfer is being sent For more information see the appropriate documentation for specific Unicenter CA XCOM Data Transport r11 platforms Note Unicenter CA XCOM Data Transport does not support the use of wildcards with PDSE program libraries For more information see PDSE Program Library Support in this chapter Library Transfers When multiple members of a PD6 are transferred and the target data set is sequential or a single member of a PDS the completion of the transfer depends on the value of the LIBNEG parameter If LIBNEG YES all selected members of the PDS are written to the larger data set If LIBNEG NO the transfer is terminated Generation Data Groups Generation Data Groups present a special problem to most file transfer systems Generally when a generation data set is uploaded into GDG a relative generation number of 1 is given as part of the filename However
401. ty 1 3 Network Levels in the SNA 1 4 2 1 4 The End User Level 2 1 4 The Logical Level 1 5 The Physical Eevel uoto nests hea Sedu Reb Diets Bibs bebe Noha hatha puis Reha pede Ree bts 1 5 Network Level Diagram 1 2 4 1 6 Benefits of LU 6 2 27 2 2 2 2 1 6 Unicenter CA XCOM Data Transport in the TCP IP 1 8 TCP IP Protocol Stagktuu u serrer eddie 1 8 Unicenter CA XCOM Data Transport Nodes in the TCP IP Network 1 10 Successtul Send File Transfer Scenario eee S u e RR eeu a e RR Ye eR REEF 1 11 Send File Flowchart 151501 RB RR 1 12 Chapter 2 The Menu Interface TSO ISPF Panels Entering the Unicenter CA XCOM Data Transport Menu Interface 2 1 Sample CUS E D ED NM eR NE 2 1 Menu Hierarchy cess 2 2 Default Values leise e em RR Rh Ro NE EMEN NER UR 2 2 Special Feat re Keys cos 2 3 Help Facility a yaaa a D eterne
402. uest that is the request that tries to execute first and the execution of which controls the subsequent execution of the other two dependent transfer requests Four XTC parameters other than XTCNET and XTCJOB are associated with the transfer request GETDATA XTCGOODREL PAYROLL means that the PAYROLL transfer belonging to the same group METS as GETDATA is to start if GETDATA completes successfully At the same time the PAYME transfer is to be purged from the transfer request queue XTCGOODPURGE PAYME However if GETDATA does not complete successfully then the PAYROLL transfer is to be purged XTCERRPURGE PAYROLL and the PAYME transfer is to start XTCERRREL PAYME Note is not supported by TYPE EXECUTE transfer requests Coding XTC Transfers in an XCOMPLEX Environment When submitted to the Admin all XTC transfers within a SYSINO1 input routed and scheduled to the same server selected for the first XTC transfer in this group TYPE SCHEDULE XTC transfers submitted through the XCOMPLEX Admin must have XTCJOB and XTCNET names that are unique to the submitted XCOMJOB Tip Use an individual s z OS TSO signon ID as the XTCNET name to make sure that it is unique The Batch Interface 3 81 SYSINO1 Parameters All transfers within each SYSINO1 must be executed released or purged and may not be extended into subsequent SYSINO1s This is because new transfers may be scheduled by the Admin to a server other than
403. umeric characters long Default XCOMDFLT The Batch Interface 3 11 PARM Parameters DISPALG DOMAIN DUMPCL 3 12 User Guide Indicates how to dispatch tasks that are ready for execution Value Definition ROTATE Tells the Unicenter CA XCOM Data Transport server to proceed to the next NSA and to dispatch it if it is dispatchable NORMAL Tells the Unicenter CA XCOM Data Transport server to scan the NSA from the top for the next dispatchable NSA Notes This parameter is valid only for the Unicenter CA XCOM Data Transport server Job DISPALG has no effect on the XCOMPLEX Admin Server Default ROTATE Identifies the Windows 2000 2003 or XP domain server used to validate the remote user ID and password Value Definition xxxxxxxxx Identifies the domain server used to validate the remote user ID and password The name can contain up to 15 characters Default None Notes Valid with TYPE EXECUTE and with transfers to Windows 2000 2003 or XP only Indicates the SYSOUT class for snap dumps trace data and other diagnostic information Value Definition x Specifies 1 alphanumeric character representing a valid SYSOUT class EDESC PARM Parameters Specifies the 16 bits coded in hexadecimal of a z OS message descriptor code Value Descriptor Definition hexadecimal Codes 8000 1 System failure 4000 2 Immediate action required 2000 3 Eventual action required 1000 4 System status 0800
404. uncated to the maximum record length N Specifies that Unicenter CA XCOM Data Transport is to terminate the file transfer upon receiving a record larger than the maximum LRECL Notes This field is supported only by the Unicenter CA XCOM Data Transport mainframe products Unicenter CA XCOM Data Transport for z OS Unicenter CA XCOM Data Transport for VSE and Unicenter CA XCOM Data Transport for VM When a record is truncated the data not within the LRECL limit is lost Default N Code Table Compression Mode Submit Job To Another System Screen This is a 3 character alphanumeric field used for specifying the translation table to be used by the remote partner for this particular transfer only This field is applicable only for transfers to Unicenter CA XCOM UNIX or Windows 2000 2003 or XP partners and only if their INTERNAL CONVERSION TABLES NO Value 1 to 3 bytes Definition Specifies up to 3 alphanumeric characters identifying the code table to be used by the remote partner Specifies whether or not Unicenter CA XCOM Data Transport compresses the data being transferred and decompresses it on the remote system Compressing the data decreases the transmission time on lower speed links Value Definition YES Provides Run Length Encoding RLE for blanks and binary zeros only NO No data compression RLE Provides complete Run Length Encoding for all characters COMPACT Provides full RLE as in RLE above
405. und on the distribution tape This illustrates JCL for a TYPE INQUIRE transfer through the XCOMPLEX Admin Server XCOMWAIT JOB 0028 CLASS A MSGCLASS X ie aa ces RUM S E ih RARE QI a eS a E ILE REN ne a sna nee NOTE THE PARM STATEMENT MAY ALTERNATIVELY BE SPECIFIED AS PARM TYPE SCHEDULE DFLTAB XCPTDFBO WHERE DEFAULT TABLE XCPTDFBO HAS CORRECT XCOMPLEX ADMIN ACBNAME PARAMETERS jp ru THIS STEP USES XCOMJOB TYPE SCHEDULE TO INITIATE A FILE TRANSFER BECAUSE THE XCOMINQ DD CARD IS INCLUDED XCOMJOB SAVES THE REQUEST NUMBER ASSIGNED TO THE TRANSFER IN THE XCOMINQ FILE THE REQUEST WILL BE ROUTED FROM THE XCOMPLEX ADMIN TO AN XCOMPLEX WORKER SERVER IS THE ACBNAME OF THE XCOMPLEX ADMIN STEPO1 EXEC PGM XCOMJOB PARM TYPE SCHEDULE ACBNAME XCPT DFLTAB XCOMDFLT STCAPPL XCPT STEPLIB DD DSN CAT CAILIB DISP SHR LOADLIB DD DISP SHR DSN CEE SCEERUN BM C RUNTIME SYSTCPD DD DSN TCPIP TCPIP DATA DISP SHR IBM TCP IP XCOMINQ DD DISP SHR DSN XCOM RBO XCOMINQ XCOMCNTL DD DISP SHR DSN XCOM RBO XCOMCNTL SYSPRINT DD SYSOUT TCP IP MSGS SYSTERM DD SYSOUT TCP IP MSGS
406. unit that can generate sessions independent of the host An ILU also meets the following criteria It utilizes LU 6 2 It works on top of PU 2 1 It functions as a primary logical unit and therefore can send a BIND It supports an extended BIND one that contains a Procedure Correlation Identifier PCID and works with the new NCP PU 2 1 support Systems that currently support ILUs include the following AS 400 z OS Windows NT SNA Server Windows NT OS 2 VM all versions Most minicomputers and UNIX workstations that support PU 2 1 Netware Independent Logical Units LU 6 2 Independent Implementations Only Type 6 logical units can be independent other LU types are dependent However not all LU 6 2 implementations are independent For example the DECnet VAX APPC version of Unicenter CA XCOM Data Transport is said to be a dependent LU because it works on top of PU 2 0 not PU 2 1 Not every LU 6 2 PU 2 1 implementation can work with independent LUs There are some aspects of PU 2 1 that NCP requires with which not all PU 2 1 implementations will work correctly This reflects the fact that not all minicomputer and PC SNA Gateway vendors had the latest NCP and VTAM for testing PU 2 1 support can be enhanced to work with ILUs without changes to Unicenter CA XCOM Data Transport NCP supports ILUs over SDLC the most common configuration using ILUs A local area network gateway attached through an SDLC link to a host
407. urce system supplies its own default value for the user ID under whose access privileges the file transfer is to execute on the source system Default TSO user ID Password Notify User Submit Job To Another System Screen Identifies the password associated with the above user ID This value is not displayed Value Definition Up to 31 Specifies up to 31 alphanumeric characters representing the alphanumeric password associated with the above user ID characters Specifies the user on the local system whom Unicenter CA XCOM Data Transport is to notify once the transfer completes Value Definition LOG Indicates that the main operator on the local computer be notified If the local computer is a z OS system a WTO macro is issued by Unicenter CA XCOM Data Transport On an AS 400 or a VAX system the operator console is notified User_id If any value but LOG is given Unicenter CA XCOM Data Transport interprets this as a specific user ID on the local system If that user is not logged on when the transfer completes the message is displayed the next time the user logs on Default TSO user ID The Menu Interface TSO ISPF Panels 2 79 Receive File From Another System Screen Receive File From Another System Screen The Receive File From Another System screen is used to provide Unicenter CA XCOM Data Transport with the information necessary to retrieve a data file from a remote system Unicenter CA XCOM r11 5 00 04 10
408. us of a file transfer request with transfer ID TUESUPDT enter TUESUPDT the transfer ID field and select all transfer categories Inactive Active Completed This provides a display containing any transfers whether they are pending in progress or completed with a transfer ID of TUESUPDT You can further limit this list by user ID remote system name a request number or a range of start and end dates and times The source for the file transfers to be displayed in the list depends on the value in the APPLID of the Unicenter CA XCOM Data Transport Server field in the Primary Option Menu By specifying the APPLID of another Unicenter CA XCOM Data Transport server you can obtain a list of the pending active and completed file transfers on that server for display or modification purposes Note If an APPLID is one of an XCOMPLEX Admin Server you can display a list of pending active and completed transfers for all XCOMPLEX Worker Servers connected to the XCOMPLEX Admin Server However changes cannot be made to this list of transfers changes can only be made when looking at an individual XCOMPLEX Worker Server transfer list The entries in the fields of the File Transfer Display Select screen are used as filters to limit the number of file transfer requests that appear in the Unicenter CA XCOM Data Transport Transfer Request Display screen A blank in any field indicates that the field should not be used as a filter that is file transfe
409. use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec TERM destname ownername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination involved in the transfer m ownername the user ID under whose security authorization the transfer is performed Using the Unicenter CA XCOM Data Transport MODIFY Commands TRACE Command Format Operands Notes Activates a Unicenter CA XCOM Data Transport internal trace Use the following format for the TRACE command F XCOM Zuname SNA 7pname The following operands are used with the TRACE command Operand Description asterisk Indicates that all active sessions involving this computer are to be traced with the asterisk operand and F XCOM TRACE without an operand are equivalent luname SNA Specifies the name 1 to 8 characters of the LU to be traced An LU name can be traced before a session exists There is no requirement that the LU be defined to allow Unicenter CA XCOM Data Transport to initiate a trace The optional keyword SNA should be used in cases where the LUNAME and IPNAME are the same at a site This forces the LUNAME to be treated exclusively as SNA when
410. using Unicenter CA XCOM Data Transport with the TCP IP option the Language Environment libraries must be concatenated next This DD statement is not required if Unicenter CA XCOM Data Transport is in the LNKLST concatenation Defines all of the Unicenter CA XCOM Data Transport parameters associated with a file transfer request Required XCOMJOB DD Statements SYSPRINT SYSTCPD XCOMGLOB XCOMINQ XCOMREST Identifies the data sets used for TCP IP messages Provides information about the configuration of the TCP IP protocol Records the current request number of an immediate transfer that is TYPE EXECUTE When the XCOMGLOB DD statement for a TYPE EXECUTE transfer is missing the request number always defaults to 2000 Sites can share this data set between jobs to ensure that all TYPE EXECUTE transfers are assigned a unique request number To update the request number for immediate transfers from TSO ISPF the XCOMGLOB and XCOMREST allocated files must be in the user s TSO logon procedure Unicenter CA XCOM Data Transport ignores the XCOMGLOB DD statement when queued transfers TYPE SCHEDULE are initiated To use this facility create a fixed block sequential data set containing an 80 byte record It is recommended that this file be included when running TYPE EXECUTE transfers utilizing the checkpoint restart feature to ensure that the request number is unique This allows the session partner to correctly identify the checkpo
411. ution tape CAI CINBOSAM XCOMUTIL Use this JCL to maintain your history file at regular intervals JOBNAME JOB ACCOUNTING XCOMHIST CLEANUP CLASS A MSGCLASS X E ICI IIS ICI II IG CII AFR CA XCOM MVS HISTORY FILE CLEANUP E 77 DELETES OLD AGED RECORDS FROM HISTORY FILE STEP DESCRIPTION auet ecc 7 1 REPRO HISTORY FILE TO WORK FILE 2 DELETE OLD RECORDS FROM WORK FILE d 3 DELETE XCOM VSAM HISTORY FILE 4 5 4 DEFINES XCOM VSAM HISTORY FILE 5 ADD VSAM SEED RECORD TO NEW HISTORY FILE 6 RELOAD HISTORY FILE FROM WORK FILE 7 DEFINE BUILD AIX S AND PATHS FOR NEW HISTORY FILE L 1 IDCAMS REPRO THE HISTORY FILE TO SEQUENTIAL FILE STEP1 EXEC PGM IDCAMS SYSPRINT DD SYSOUT DD1 DD DSN XCOM X XCOMHIST DISP SHR DD2 DD DSN amp amp HSTSAV UNIT SYSALLDA SPACE CYL 2 2 DISP NEW PASS DCB RECFM VB LRECL 2000 BLKSIZE 23440 SYSIN DD REPRO IFILE DD1 OFILE DD2 IT STEP2 EXEC PGM XCOMUTIL COND 0 NE STEPLIB DD DSN XCO
412. vectors to override the PLU name in the user portion of the BIND This is required for some systems such as AS 400 For detailed information see specific system components Value Definition xxxxxxxx Specifies up to eight alphanumeric characters indicating a name to override the PLU name for remote systems in CINIT and BIND vectors Notes Do not confuse this parameter with the VTAM parameter NETID Default XCOMAPPL The Batch Interface 3 21 PARM Parameters SECURE SCHEDULE Specifies whether a secure SSL TCP IP connection is to be used to perform the SCHEDULE or INQUIRE operation against the target server Value Definition YES A secure SSL TCP IP connection is to be used by XCOMJOB to connect to the target server referenced in the STCIP parameter NO A regular TCP IP connection is to be used Notes This parameter applies only to SCHEDULEs or INQUIREs using TCP IP It has no meaning for SNA based operations Default The default value is determined by the SSL and SECURE SOCKET parameter combinations in the Default Options Table STCAPPL Identifies the APPLID of the Unicenter CA XCOM Data Transport server to which this request is to be queued Value Definition XXXXXXXX Specifies up to eight alphanumeric characters indicating the Unicenter CA XCOM Data Transport server where this request is to be queued Notes STCAPPL is necessary when there are several Unicenter CA XCOM Data Transport servers running on
413. verride default and propagated space and DCB values for new z OS data sets Unicenter CA XCOM Data Transport features a Help facility which provides help information for every Unicenter CA XCOM Data Transport screen You can obtain help information by using the PF1 key a When you wish to obtain help for a particular field place your cursor on that field and press PF1 m Pressing PF1 when the cursor is on the COMMANDS line allows you to start a Unicenter CA XCOM Data Transport tutorial session with the current screen as its starting point The Menu Interface TSO ISPF Panels 2 3 The Primary Option Menu m When a message is displayed pressing PF1 provides help for that message m To cancel a help session and return to the starting point press The Primary Option Menu The XCOM Selection Menu is the entry point for the Unicenter CA XCOM Data Transport Menu Interface screens Four options are provided In addition to selecting a menu option certain primary processing parameters may be specified on this screen The values entered are retained on all subsequent screens for this transfer but can be overridden by typing in new values XCOMPRIM 05 03 31 Unicenter CA XCOM r11 5 00 TURKIO1 Primary Option Menu Send Files Reports Jobs 1 1 Send Files 1 2 Send Reports 1 3 Send Jobs 2 Receive Files 3 XCOM Operator Control Remote System Identification IP Dest 123 123 123 123 Port 4567 551 YES CONFIG SSL or S
414. whether record separators such as carriage returns are added to the data delimiting records when they are written Note This parameter is ignored if both the sending and receiving systems are EBCDIC Value Definition YES Add separators to the data delimiting records NO Do not add separators Notes If PACK LENGTH is coded then you must also code RECSEP NO When transferring a text file to a partner that supports record separators for example CRLF 0D0A on NT and LF 0A on UNIX record separators are inserted No separators are inserted in binary files transferred with PACK LENGTH Default YES Specifies the space to be allocated for a z OS file Value Definition CYL TRK or This value is specified in the following format BLK for alloc 0 to 9999 for pri SPACE alloc pri sec dir alloc Specifies cylinders CYL tracks TRK or blocks BLK for storage pri Specifies the primary space allocation sec Specifies the secondary space allocation dir Specifies the number of directory blocks for partitioned data sets UNIT VOL SYSINO1 Parameters Notes This parameter is only used when creating a file under a system such as z OS that pre allocates space For more information refer to documentation on the z OS JCL SPACE parameter in the DD statement Default Unicenter CA XCOM Data Transport Default Options Table defaults Indicates the unit type where the data set is to be created
415. wn routines at various positions known as exit points in the source code This appendix provides information about all currently available user exits The information provided about each user exit includes m Purpose m Module name and entry point m Method of enabling the user exit m Name of the Unicenter CA XCOM Data Transport module from which the user supplied module is called m Method of entry implying the relationship between the two modules m Name of the required DSECT m Addressing mode at entry m Information about entry registers m Information about exit registers m Return codes m Location of a sample program Important If you are upgrading to a new release you need to reassemble and link edit your user exit programs User Exits D 1 User Exit 1 User Exit 1 Purpose This exit allows the execution of a user developed exit routine upon completion of a Unicenter CA XCOM Data Transport file transfer The Unicenter CA XCOM Data Transport history record data is available for interrogation at this point Module Name and Eniry Point The module name and entry point for this exit is XCOMEX01 How to Enable Specify EXITO1 YES in the Default Options Table to enable this exit Calling Module The module XCOMXFER calls this exit Entry Method This exit is attached as a subtask by Unicenter CA XCOM Data Transport Required DSECT SMFDSECT is the required DSECT Addressing Mode at Entry The addressing mode at entry is 31 Regis
416. wo new generations of the GDG The first version contains garbage because it was allocated by the z OS JCL processor and was never opened or closed by a program to write an end of file mark If the transfer fails under certain conditions the version allocated by the Unicenter CA XCOM Data Transport started task may be deleted This leaves the version of the GDG allocated by the z OS JCL processor as the current version All of these potential problems can be avoided if the LOCAL FILE name is specified on the LFILE SYSINO1 parameter rather than with the LCLDS01 DD statement for TYPE SCHEDULE transfers The LCLDS01 DD statement permits sequential data sets to be concatenated for TYPE EXECUTE requests Other types of data sets may not be concatenated If it is necessary to send more than one data set to the same remote file using non sequential data sets or if the transfer is a TYPE SCHEDULE request the Unicenter CA XCOM Data Transport Transfer Control XTC facility should be used see the sections SYSINO1 Transfer Control XTC Parameters and Coding Interdependent Transfers Note The SYSOUT keyword cannot be used in this DD statement Defines the library containing Unicenter CA XCOM Data Transport load modules and if Unicenter CA XCOM Data Transport is used with the TCP IP option the Language Environment libraries A JOBLIB or STEPLIB statement should be included to identify the Unicenter CA XCOM Data Transport load library If you are
417. word use the following format oldpassword newpassword PASSWORD should not be confused with LPASS see above The Batch Interface 3 47 SYSINO1 Parameters PROGLIB RESTART 3 48 User Guide Specifies whether the transfer is of a PDSE program library or not Value Definition YES Indicates the transfer of a PDSE program library NO Indicates the transfer is not of a PDSE program library Notes This parameter applies only to mainframe SMS data sets Unicenter CA XCOM Data Transport uses the values from PSOPREF and PSOVOL to create the temporary data sets used in transferring PDSE program libraries Only whole PDSE program libraries may be transferred The transferring of an individual member or the use of wild cards for example ABC to transfer multiple members is not supported PROGLIB YES requires the use of an XCOMPRNT DD statement Ensure any Unicenter CA XCOM Data Transport for z OS servers used to send or receive PDSE program library transfers have been modified to include the XCOMPRNT DD See sample member XCOM in the appendix Sample Files If PROGLIB YES is used in TYPE EXECUTE transfers then XCOMPRNT DD must be included in the batch XCOMJOB JCL Default None Identifies whether a stopped transfer should be restarted from the nearest checkpoint or from the beginning This option is only valid for TYPE EXECUTE transfers and it is used only if a problem occurred earlier on the restart checkpoint and the
418. xecution Priority Local File Name Receive File From Another System Screen Specifies the execution priority for this request Value Definition 1 to 255 Specifies a priority to provide efficient scheduling in a busy transfer environment 1 is the lowest execution priority Notes When multiple Unicenter CA XCOM Data Transport transmissions are executing concurrently transfers with higher execution priorities receive preferential service In a busy Unicenter CA XCOM Data Transport environment unless you have compelling reasons for not doing so enhance processing efficiency by giving short file transfers a higher priority value than long running transmissions Default 16 Indicates the name of the data set where the file being retrieved will be stored Value Definition Up to 56 Specifies up to 56 characters consisting of the following alphanumeric A 1 to 44 character data set name characters An optional member name enclosed in parentheses Optional single quotation marks apostrophes to enclose the data set The user s TSO profile prefix is inserted at the beginning of this entry unless the entry is enclosed in single apostrophes If the TSO profile is set to NOPREFIX nothing is inserted Default The last data set name entered The Menu Interface TSO ISPF Panels 2 81 Receive File From Another System Screen Remote System Identification 2 82 User Guide Indicates the destination from which the file i
419. y Requirements SNAP Command Format The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name READ XCOM applsec SHOW destname ownername The variables represent the following values m applsec the value of the APPLSEC parameter in the Default Options Table m destname the name of the destination involved in the transfer ownername the user ID under whose security authorization the transfer is performed Note ISPF and CICS display requests may cause resource access checking for both SHOW and RSHOW commands Produces a snap dump of the Unicenter CA XCOM Data Transport region F XCOM SNAP Important It is best not to use the SNAP command unless instructed by the Unicenter CA XCOM Data Transport technical support staff Command Security Requirements The use of the command requires that the command issuer s security authorization contain the following access level and resource specifications for CLASS OPERCMDS Access Level Resource Name UPDATE XCOM applsec SNAP The applsec variable represents the value of the APPLSEC parameter in the Default Options Table Operation and Control 6 39 Using the Unicenter CA XCOM Data Transport MODIFY Commands STAT Command Format Operands For the XCOMPLEX Admin Server only The STAT command displays statistics for each XCOMPLEX Wo
420. y and are noted as such 6 4 User Guide MODIFY Command Format Using the Unicenter CA XCOM Data Transport MODIFY Commands The general format of the MODIFY commands is as follows F MODIFY procname operana1 211 The following table explains the function of each MODIFY command element Command Element F MODIFY procname command operand1 operand2 Description The keyword MODIFY which can be abbreviated to F identifies the following string of comma separated tokens as a MODIFY command The name of the Unicenter CA XCOM Data Transport server XCOMPLEX Worker Server or XCOMPLEX Admin Server The Unicenter CA XCOM Data Transport MODIFY command to be performed The first and second operand qualifying the MODIFY command Note The number of operands that need to be specified depends on the command Note If you use NETVIEW you can enter Unicenter CA XCOM Data Transport commands through NETVIEW To do this preface the standard Unicenter CA XCOM Data Transport command with MVS For example MVS F XCOM DIS destname Operation and Control 6 5 Using the Unicenter CA XCOM Data Transport MODIFY Commands Notational Conventions 6 6 User Guide The following table explains the notational conventions used in the description of the Unicenter CA XCOM Data Transport Modify commands and in the specification of resource names Convention UPPERCASE lowercase italics MI
421. y be specified The equivalent DFLTAB option is included to describe each override parameter m TMYES to force TAPEM YES for this file m IMNO to force TAPEM NO for this file m IMEPIC to force TAPEM EPIC for this file Note The override applies only to the processing for the file whose data set name is on the statement that the override appears on It is in effect for this transfer only VSAM Managed SAM Naming Conventions Use the following format to name a VSAM managed SAM file file id M prim recs secfrecs catalog id The following table describes the parts of a VSAM managed SAM file name Part file id M prim recs sec recs 9 24 User Guide Description The name that identifies this data set that will be implicitly defined to VSAM at open time Range 1 to 44 characters Indicates that this is a VSAM managed SAM file Note If you enter a transfer request from a platform that has not yet implemented the extended tape processing parameters or menu interface fields for controlling tape processing to a Unicenter CA XCOM Data Transport VSE server you must use the T option You are restricted to standard label tape processing Used for output files only This indicates the number of blocks of the size defined by the BLKSIZE parameter for the primary data set allocation Used for output files only This indicates the number of blocks for the secondary data set allocation If no secondary allocation is coded
422. your system and during third party transfers when you wish to send a file from a server other than your own to a third remote system Only TYPE SCHEDULE transfers are valid for third party initiates 3 22 User Guide STCIP STCPORT SWAIT PARM Parameters Indicates to XCOMJOB the IP address that is the target of a SCHEDULE or INQUIRE Value Definition 1 to 63 Specifies the address of the started task node with a name alphanumeric which must be defined or known to the domain name characters server nnn nnn nnn nnn Specifies the address of the remote IP node with a number in dotted decimal notation Specifies to XCOMJOB the IP PORT of the started task that is the target of the SCHEDULE or INQUIRE Value Definition 1 to 65535 Specifies a number that indicates the IP port of the started task Default If the STCPORT parameter is not specified the IPPORT parameter value defined in the Unicenter CA XCOM Data Transport Default Options Table is used Specifies the number of seconds that Unicenter CA XCOM Data Transport waits for a session to be established after the request for session establishment has been queued Value Definition 1to32767 Specifies the time limit in seconds within which a queued session establishment request must result in the establishment of a session Default 30 The Batch Interface 3 23 PARM Parameters TCPSTACK TIMEOUT 3 24 User Guide Notes If Unicenter CA XCOM Data Transport s

Unicenter CA-XCOM Data Transport for z/OS User Guide

Contents

Download Pdf Manuals

Related Search

Related Contents