II13229: Z/OS CS V1R2: SC31-8783-01 IP MESSAGES: VOLUME 1 (EZA) TCPIPINFO BOOKAPAR

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • INTRAN

Error description

Local fix

  • ************************************************************
    Modified EZA8582E as follows:
    New User or Operator Response: Verify that the data set is
      protected. Use the DATESET parameter passed to SMTPNOTE
      to specify a different data set to be used. If that is not
      the problem, notify the system programmer of the error.
    New System Programmer Response: SMTPNOTE uses the TSO
      allocation (alloc) command  to create a temporary data
      set similiar to the data set passed on the DATESET
      parameter. The allocatation command is failing. Use the
      messages issued by the  operating system to determine the
      cause of the error and respond as indicated. For more
      information, see the z/OS TSO/E Command Reference.
    ************************************************************
    Modified EZA8583E as follows:
    New Message Text:
    EZA5583E UNABLE TO USE DATASET data_set, COPYING ERRORS
             DETECTED
    New User or Operator Response: Verify that the data set
      logical record (LRECL) attribute is 243 or less. Also,
      verify that the data set is not being shared with other
      users when SMTPNOTE is executed. If this is not the
      problem, notify the system  programmer of the error.
    New System Programmer Response: SMTPNOTE used the TSO REPRO
      command to copy the user's data into a temporary data set.
      This command is failing. Use the messages issued by the
      operating system to determine the cause of the error and
      respond as indicated. For more information, see the z/OS
      DFSMS Access Method Services for catalogs.
    ************************************************************
    In message EZA5559I, changed:
    Source Data Set to SMTPQUEU
    Procedure Name to DisposeSitePtr
    **************************************************************
    Added the following new message:
    ********************
    EZA2300I Command ended because the CPU time limit was exceeded
    Explanation: The FTP client was processing a command when the
    process was stopped either because the CPU time limit was
    exceeded or by an OMVS kill -SIGXCPU command.
    System Action: The FTP client ends.
    User or Operator Response: Contact the system programmer.
    
    System Programmer Response: If the client process was stopped
    due to CPU time limit exceeded, increase the CPU time allocated
    to the FTP client.
    Source Data Set: EZAFTPCX
    Procedure Name: pgmxcpuc
    ************************************************************
    Updated the following fields in message EZA2564W:
    ********************
    User or Operator Response: Rerun the FTP with tracing turned on.
    Contact the system programmer.
    System Programmer Response: Look at the trace and find one of
    the following trace entry sequences:
    * seq_open_file: xyz -> ...
      seq_open_file: failed (aa): bbbb
    
    The first line describes open mode with values x, y, and z that
    are defined as follows:
       x = I --> Input
       x = O --> Output
    
       y = S --> Stream I/O
       y = R --> Record I/O
    
       z = B --> Binary stream
       z = T --> Text stream
    The second line describes the error that occurred. aa is the
    errno value returned from the fopen of file. bbbb is the text
    associated with the errno value. The following describe values
    and text that could be observed:
    (61): Error trying to define file
          The file is already opened.
    
     * seq_open_file: Using BSAM, I, SYS00006, , 29
          0, 0, 0
       seq_open_file: BSMOP returned NULL, rc xxx, reason yyy
    The second line describes the error which occurred on the open.
    Use the return code (rc) and reason code to determine why the
    error occurred.
    
    For return code 80a, reason code 10, or return code 4, FTP was
    unable to obtain storage to open the dataset. Increase the
    region size for the FTP job or user.
    ************************************************************
    Added the following new message:
    ********************
    
    EZA2825E File contains records that are too long to be processed
    Explanation: The FTP client cannot process the received data
    because a record delimiter was not found in the data and the FTP
    client is not configured to wrap records. The FTP client expects
    to find a record delimiter, such as a Carriage Return and Line
    Feed (CRLF) in ASCII mode or a Newline(NL) in EBCDIC mode, to
    denote the end of a record.
    
    System Action: The file is not transferred.
    User or Operator Response: Ensure that the ASCII or EBCDIC file
    being received has proper delimiters in the data or configure
    the FTP client to wrap records using the wraprecord parameter.
    Refer to z/OS Communications Server: IP Users Guide and Commands
    for information about configuring wraprecord.
    System Programmer Response: None.
    Source Data Set: EZAFTPCG
    Procedure Name: mvs_rcvFile()
    ************************************************************
    Added the following note to the message Explanation field in
    EZA2536I:
    ********************
    Note: For smaller files (less than 360 KB), the reported time
    (and calculated rate) value reflects the amount of time to
    transfer the file to the TCP transport layer more than it
    reflects the network rates.
    ************************************************************
    Added the following missing message:
    ********************
    EZA1645I LRECL lrecl is invalid for RECFM recfm
    Explanation: After processing the LOCSITE LRECL=lrecl command,
    the client cross checked the new values of the RECFM and LRECL
    variables and found them to be set to a combination that is
    invalid for the MVS operating system.
    
    System Action: The LRECL value is changed to the nearest value
    that is compatible with the record format. This message should
    be followed by EZA2791I, indicating the new value of the LRECL.
    User or Operator Response: If the new value for the LRECL is
    acceptable, no action is necessary, otherwise change the RECFM
    and LRECL to valid values.
    
    System Programmer Response: Use LOCSITE to set the correct
    values for RECFM or LRECL. Refer to z/OS DFSMS: Using Data Sets
    for information about selecting valid values for BLOCKSIZE,
    LRECL, and RECFM.
    Source Data Set: EZAFTPMK
    Procedure Name: SiteCheck
    

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II13229

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2002-04-04

  • Closed date

  • Last modified date

    2003-06-27

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

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

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

001

Operating system(s):

MVS, OS/390, VSE/ESA, z/OS, z/VM

Reference #:

II13229

Modified date:

2003-06-27

Translate my page

Machine Translation

Content navigation