Sending Reports with PSO (JES Spool) with XCOM for z/OS

Products

• XCOM Data Transport - z/OS

Issue/Introduction

XCOM scans the JES queue automatically for reports to transfer to remote partners. XCOM selects reports either by WRITER or DEST.
 

1. XCOM scans the JES Spool at the JESINTV specified in the Config Member or XCOM default table. This value is specified in seconds. Scanning cannot be turned off.
    
2. Report transfers are single threaded. Only one report is sent to each destination per scan of the spool.
    
3. The MAXRPTB parameter in the default table or config member specifies the maximum block size in bytes that XCOM uses to write reports on the spool.
    
4. Temporary report datasets are written according to the PSOVOL and PSOUNIT specified in the default table of config member and start with a high level qualifier specified by PSOPREF in the default table.
    
5. If PSOSECUR=YES, EXIT05 will be called.
    
6. The PSODISP parameter in the default table specifies what happens to the temporary report dataset on the JES Spool if the report cannot be delivered. If PSODISP=KEEP, these temporary datasets are retained if there is a problem. If PSODISP=DELETE, these temporary datasets are deleted if there is a problem and the report must be requeued to try again.
    
7. 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.

Environment

Release:XCOM Data Transport-for z/OS
Component:

Resolution

  Setup

1. Define a destination member of TYPE=DEST enabled for the remote partner. The destination member must contain either
   
   DEST=XCOM or
   WRITER=XCOM
   
   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 below)
    
2. If the destination is a TCPIP destination, then TCPSESS must be set to at least 2.
    
3. Security must permit XCOM to access the reports on the spool.

   Troubleshooting

1. Reports just don't go
    
   
   1. Check the XCOMLOG and the JES Log for any messages.
       
   2. Disable and reenable the dest member
       
   3. Display the report on the JES Spool. Make sure that the dest member matches the attributes of the report on the JES Spool. If the REPORT is specified as DEST= in the destination member, it must show up as DEST on the SPOOL. If WRITER in the dest member, WRITER must show up. The writer or dest names must match.
       
   4. List the destination member
      /F xcomprocname,LIST,destmembername The output is written into the XCOM log.
   5. Reset the destination member
      /F xcomprocname,RESET,*
       
   6. Review security. If XCOM does not have the proper permissions, it cannot pick up any reports. It may not even be able to detect that there are any reports out there.
       
   7. Make sure that reports are not queued in a held class.
       
2.  The reports are picked up, but they do not reach the partner
    
   
   1. Check the XCOMLOG and the JES Log for any messages.
       
   2. Depending on the problem, check the PSOVOL for space or security problems. PSODISP=KEEP can cause temporary datasets to build up.

Additional Information

SAMPLE JCL to queue as DEST
//STEP001 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=XCOM.TEST.TRANSFER,DISP=SHR
//SYSUT2 DD SYSOUT=1,DEST=XCOMABC
//SYSIN DD DUMMY

SAMPLE DEST MEMBER (dest)
TYPE=DEST
DEST=XCOMABC
IPNAME=192.0.21

SAMPLE JCL to queue as WRITER
//STEP001 EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=A,HOLD=NO
//SYSIN DD DUMMY
//SYSUT1 DD DSN=XCOM.TEST.TRANSFER,DISP=SHR
//SYSUT2 DD SYSOUT=(A,XCOMABC)

SAMPLE DEST MEMBER (writer)
TYPE=DEST
WRITER=XCOMABC
IPNAME=192.0.2.2