PK01360: TSO RSH AND REXEC DO NOT RETURN REMOTE EXECUTION SERVER ERROR MESSAGES IN SYSPRINT DD LOCATION GOES TO SYSOUT INSTEAD.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In z/OS V1R5 and V1R6 Comm Server IP any error messages from a
  remote execution server that was started by batch submitted
  MVS or TSO REXEC or RSH commands does not return error
  information into the same location as in z/OS V1R4 and earlier.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release 5 and 6 IP:       *
  *                 TSO REXEC/RSH                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Batch jobs executing the TSO REXEC or   *
  *                      RSH client command by using PGM=RSH,    *
  *                      PGM=REXEC or PGM=IKJEFT01 will have     *
  *                      error messages written to SYSOUT.       *
  *                      SYSOUT will be used even if a //OUTPUT  *
  *                      or //SYSPRINT DD is specified.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The TSO REXEC and RSH clients wrote error messages
  directly to stderr even if the //OUTPUT or //SYSPRINT DD
  statements were specified in a batch job.
  For migration reasons the //OUTPUT or //SYSPRINT specified
  location in a batch job will be used to receive error output.
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

• When executed in a batch job the TSO REXEC and RSH client code
  has been changed to use the //OUTPUT DD location for error
  messages. If the //OUTPUT DD is not available then the
  //SYSPRINT DD location will be used.
  If neither DD is available then any error messages will be
  written to stdout.
  
  When the TSO REXEC and RSH client code is executed in an
  interactive TSO environment error messages will be written to
  the OUTPUT DD if specified. If no OUTPUT location is allocated
  the error messages will be written to stdout.
  
  * Cross Reference between External and Internal Names
  EZATREXE (TSOREXEC)  EZATRSH  (TSORSH  )  EZATREXE (TSOREXEC)
  EZATRSH  (TSORSH  )
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UK01856 UK01855 PK05741

Modules/Macros

• EZATREXE EZATRSH
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R150 PSY UK01855

     UP05/04/23 P F504

• R160 PSY UK01856

     UP05/04/23 P F504

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.