Action Code A01:

 

Enable the CONNX DEBUG Trace and Send the Trace Output to CONNX Technical Support

If the SAS/C STDERR DDNAME points to a JES SYSOUT dataset or to a physical sequential data set, browse the output for SAS/C runtime library error messages.  In some cases, these messages may be sufficent to diagnose the error scenario.

By default, both the STDERR and STDOUT DDNAMES are dummied out in JCL procedures CNXVSAM and CNXVSCT, which reside in the CONNX JCL dataset (default name = CONNX.VVRR.STASK.CNTL).
 

//STDERR       DD DUMMY

//STDOUT       DD DUMMY
 

If the CONNX VSAM / QSAM / PDS listener program is executed as a started task, change the started task DDNAME definitions to point to the pre-allocated *.STDERR and *.STDOUT datasets; for example:
 

//STDERR DD DSN=CONNX.VVRR.STASK.STDERR,DISP=SHR

//STDOUT DD DSN=CONNX.VVRR.STASK.STDOUT,DISP=SHR
 

If the CONNX VSAM / QSAM / PDS listener program is executed as a batch job, add overrides to the execution JCL member (default = CNXVSAMJ):
 

//CNXRUNB.STDERR DD DSN=CONNX.VVRR.STASK.STDERR,DISP=SHR

//CNXRUNB.STDOUT DD DSN=CONNX.VVRR.STASK.STDOUT,DISP=SHR
 

Pointing DDNAME STDERR to SYSOUT or to a sequential dataset will capture SAS/C runtime library error messages.  For further diagnostic messages, enable the CONNX debug trace logic by setting the CONNX DEBUG environment variable to 1.  To do so, refer to the CONNX online help file Installation Guide and drill down to:  

Step 5: Install IBM Mainframe-Compatible Server + CONNX for VSAM / QSAM / PDS +

Part 3: CONNX TSO Configuration Utility + CONNX Environment Variables + To define unique CONNX environment variables per Started Task / Batch Job.  

Find the current control record member used to define CONNX environment variables in the CONNX *.CNTL partitioned data set (default = CNXPARMS) and change the =DEBUG environment variable to 1:
 

=DEBUG=1
 

Next, stop the CONNX VSAM / QSAM / PDS Started Task / Batch job TCP/IP listener program (CNXRUNB).  Refer to the CONNX online help file Installation Guide and drill down to:

Step 5: Install IBM Mainframe-Compatible Server + CONNX for VSAM / QSAM / PDS +

Part 3: CONNX TSO Configuration Utility + To stop the CONNX Started Task/Batch Job TCP/IP Listener

Restart the the CONNX VSAM / QSAM / PDS Started Task / Batch job TCP/IP listener program (CNXRUNB) by submitting the execution JCL (CNXVSAMJ) or by starting the started task (CNXVSAM).

 

Re-run the problem scenario from the client PC(s).  If the trace logic has been successfully enabled, the *.STDOUT physical sequential dataset will contain CONNX debug messages;  additional SAS/C runtime library error messages, if any, will be written to the *.STDERR physical sequential dataset.

Send both trace output datasets via email to CONNX Technical Support at support@connx.com .

After successfully generating a CONNX trace, remember to disable the CONNX trace logic by resetting the DEBUG environment variable in the CNXPARMS member of the CONNX *.CNTL partitioned data set to 0:
 

=DEBUG=0
 

Next, reinstate the STDERR and STDOUT DDNAMEs to DUMMY in the CNXVSAM JCL procedure:
 

//STDERR       DD DUMMY

//STDOUT       DD DUMMY
 

If the CONNX VSAM / QSAM / PDS listener program is executed as a batch job, remove the overrides to the execution JCL member (default = CNXVSAMJ):
 

//CNXRUNB.STDERR DD DSN=CONNX.VVRR.STASK.STDERR,DISP=SHR

//CNXRUNB.STDOUT DD DSN=CONNX.VVRR.STASK.STDOUT,DISP=SHR
 

Finally, stop and restart the CONNX VSAM / QSAM / PDS TCP/IP listener program as documented above.