How to use TYPE=SCHEDULE with XCOM for z/OS

Products

• XCOM Data Transport
• XCOM Data Transport - Windows
• XCOM Data Transport - Linux PC
• XCOM Data Transport - z/OS

Issue/Introduction

Using PARM parameters with TYPE=SCHEDULE JCL.

When you send an XCOM transfer to the XCOM Server on the mainframe (TYPE=SCHEDULE) or execute it directly (TYPE=EXECUTE) the transfer is using an ACB, regardless if the transfer itself is using TCP/IP or SNA. You can see that an ACB was used in messages:

  XCOMM0008I XCMLS200 ACB OPENED SUCCESSFULLY
  and
  XCOMM0015I XCMLS200 ACB CLOSED SUCCESSFULLY

appearing in the Joblog. When TCP/IP is used as medium, that ACB will not be used. But if there is no ACB available, the transfer fails.

Environment

Release:
Component: XCMVS

Resolution

• Add parameters SNA=NO to the Default Table or config member you are using.
• When doing a TYPE=SCHEDULE transfer via the XCOM-Server you need to specify the location of the Server using parameters STCIP and STCPORT in the PARM-Statement of the Transfer-Job. If you omit that, the result may be this message:

XCOMM0817E STCIP= PARAMETER MISSING - CANNOT CONNECT TO SERVER

and the Job fails.

• The IP-Address and the Port the XCOM-Server is listening on are documented in the Job-Log of the Server:

XCOMM0788I XCOM TCP/IP LISTENER ACTIVE ON PORT nnnnn, STACK TCPIP
XCOMM0819I TCP/IP FUNCTION GETHOSTID RETURNS ADDRESS nnn.nnn.nnn.nnn

• The PARM-statement looks like this:

//    PARM=('TYPE=SCHEDULE',
//    'DFLTAB=<name_of_Default_table>',
//    'STCIP=nnn.nnn.nnn.nnn',
//    'STCPORT=nnnnn')

For example,
//STEP01 EXEC PGM=XCOMJOB, 
// PARM=('TYPE=SCHEDULE,ACBNAME=XCOM') ,STCAPPL=XCOMAPP1') 
NOTE: If you are using the default port, you may omit the STCPORT parameter.

Additional Information

For additional information about TYPE=SCHEDULE, refer to Perform a Scheduled Transfer (TYPE=SCHEDULE) in our online documentation.