PM61598: Occasionally when RDz LPEX editor is used to open a file with an LRECL ? 80 bytes, file records are truncated at 80 bytes.

APAR status

• Closed as program error.

Error description

• When sequential file is opened using the RDz LPEX editor and the
  file has an record length (LRECL) ? then 80 bytes, the file
  records get truncated at 80 bytes.  The attributes of this file
  in the properties view appear as undefined.  The following
  exception appears in user's rsecomm.log:
  
  !MESSAGE CRRZI0380E No response from TSO command server.
  !STACK 0
  org.eclipse.rse.services.files.RemoteFileException: CRRZI0380E
  No response from TSO command server.
      at com.ibm.ftt.resources.zos.util.RSEClient.command(Unknown
  Source)
      at com.ibm.ftt.resources.zos.util.RSEClient.command(Unknown
  Source)
      at com.ibm.ftt.resources.zos.util.RSEClient.command(Unknown
  Source)
      at com.ibm.ftt.resources.zos.util.RSEClient.command(Unknown
  Source)
      at com.ibm.ftt.resources.zos.util.RSEClient.command(Unknown
  Source)
      at
  com.ibm.ftt.resources.zos.filesystem.impl.DataSetImpl.getAttribu
  tes(Unknown
  Source)
      at
  com.ibm.ftt.resources.zos.filesystem.impl.DataSetImpl.listds(Unk
  nown
  Source)
      at
  com.ibm.ftt.resources.zos.zosphysical.impl.ZOSDataSetImpl.getCha
  racteristics(Unknown
  Source)
      at
  com.ibm.ftt.lpex.mvs.editor.MvsLpex.initializeRecordLengthParame
  ters(Unknown
  Source)
      at com.ibm.ftt.lpex.mvs.editor.MvsLpex.updateProfile(Unknown
  Source)
  
  In each case reported, the file had an LRECL = 133 and RECFM of
  FBA.  This problem does not occur every time the file is opened
  using RDz.
  

Local fix

Problem summary

• When the RDz client wants to know the record length of the
  dataset, the RDz client sends C_LIST_DATASET command to the
  remote host, which is sent to the TSO command server.  The
  TSO command server does not respond to the command occasionally.
  

Problem conclusion

• The record length can be retrieved as a data set attribute
  without using the TSO command server.  Now the client will try
  to get the record length as an attribute.
  
  The problem listed in this APAR has been resolved with
  IBM Rational Developer for System z V8.0.3.3 Fix Pack which
  is available from the Recommended Fixes support download page:
  http://www-1.ibm.com/support/docview.wss?rs=2294&uid=swg27006335
  

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:

Fix information

• Fixed component name

  RATL DEV FOR SY

• Fixed component ID

  5724T0700

Applicable component levels

• R803 PSY

     UP