Troubleshoot Sending Reports with PSO

The following list shows problems and possible solutions for sending reports with PSO:

Reports just do not go

Possible solutions:

Verify that PSO support is enabled for the CA XCOM Data Transport server. PSO can be disabled by specifying PSO=NO on the XCOMXFER PARM.
Check the XCOMLOG and the JES Log for any messages.
Disable and reenable the dest member
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.
List the destination member:
```
/F xcomprocname,LIST,destmembername
```
The output is written into the XCOM log.
Reset the destination member:
```
/F xcomprocname,RESET,*
```
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.
Make sure that reports are not queued in a held class.
Check the XCOMLOG and the JES Log for any messages.
Depending on the problem, check the PSOVOL for space or security problems. PSODISP=KEEP can cause temporary data sets to build up.

The reports are picked up, but they do not reach the partner

Possible solutions:

Check the XCOMLOG and the JES Log for any messages.
Depending on the problem, check the PSOVOL for space or security problems. PSODISP=KEEP can cause temporary data sets to build up.