CA XCOM XTC Schedule Process over PLEXQ Scheduling to Different Servers

Products

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

Issue/Introduction

XTCNET transfers can be scheduled to different servers if the first transfer in the job is not part of the XTCNET.  This causes XTC jobs not to be released.​

PLEXQ ID=#XCOML0000 
PLEXQ #XCOML0000 IPNAME=XCOMC 
PLEXQ #XCOML0000 TYPE=SEND 
PLEXQ #XCOML0000 FILETYPE=FILE 
PLEXQ #XCOML0000 FILEOPT=CREATE 
PLEXQ #XCOML0000 MGMTCLAS=MCHLOG 
PLEXQ #XCOML0000 LFILE= XCOM.R12.MVSZ
PLEXQ #XCOML0000 FILE= XCOM.R12.MVSZ
PLEXQ #XCOML0000 NEWXFER 
PLEXQ #XCOML0000 TYPE=SEND 
PLEXQ #XCOML0000 LFILE= XCOM.R12.CNTL(MVSJOB1)
PLEXQ #XCOML0000 FILETYPE=JOB 
PLEXQ #XCOML0000 XTCNET=MVSDSS 
PLEXQ #XCOML0000 XTCJOB=MVSJOB 
PLEXQ #XCOML0000 HOLD=YES 
PLEXQ #XCOML0000 NEWXFER 
XCOMM0027I XCOMRANQ ESTAE ROUTINE HAS BEEN ESTABLISHED 
PLEXQ #XCOML0000 FILETYPE=FILE 
XCOMM1168I PLEXQ LISTENER TASK STARTING 
PLEXQ #XCOML0000 FILEOPT=CREATE 
PLEXQ #XCOML0000 LFILE= XCOM.R12.MVSF
PLEXQ #XCOML0000 FILE= XCOM.R12.MVSF
PLEXQ #XCOML0000 HOLD=NO 
PLEXQ #XCOML0000 XTCNET=MVSDSS 
PLEXQ #XCOML0000 XTCGOODREL=MVSJOB 
PLEXQ #XCOML0000 XTCERRPURGE=MVSJOB 
XCOMM0297I REQUEST PROCESSED ON LOCAL SYSTEM 
XCOMM1101I CONNECTED TO PLEXQ GROUP XCOMADM AS M1111 
XCOMY 031690 #XCOML0000 XCOMM0300I REQUEST # 031690 PROCESSED SUCCESSFULLY TO PLEXQ: XCOMADM / XCOMY 
XCOMM0297I REQUEST PROCESSED ON LOCAL SYSTEM 
XCOMZ 010849 #XCOML0000 XCOMM0300I REQUEST # 010849 PROCESSED SUCCESSFULLY TO PLEXQ: XCOMYADM / XCOMZ 
XCOMM0297I REQUEST PROCESSED ON LOCAL SYSTEM 
XCOMY 031691 #XCOML0000 XCOMM0300I REQUEST # 031691 PROCESSED SUCCESSFULLY TO PLEXQ: XCOMADM / XCOMY 
XCOMM1102I DISCONNECTED FROM PLEXQ GROUP XCOMADM
 

Environment

z/OS

Cause

PLEXQ Scheduling did not handle the particular case where the first transfer in the job is not part of the XTCNET.

Resolution

Apply XCOM for z/OS 12.0 Solution SO01202 PLEXQ-SCHEDULED XTCNET TRANSFERS MAY GO TO DIFFERENT SERVERS