OA30756: RECEIVE ICH408I OMVS SEGMENT NOT DEFINED WHEN STARTING I/O OPS.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When starting I/O OPS message ICH408I JOB(IOOPS) STEP(IOOPS)
    CL(PROCESS ) OMVS SEGMENT NOT DEFINED is received.  There is no
    OMVS segment defined for I/O OPS.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Customers running SA 3.2 I/O operations      *
    *                 without COMM= start-up parameter but no      *
    *                 TCP/IP.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When I/O-Ops is started without the     *
    *                      COMM parameter it first tries to        *
    *                      establish a TCP connection. This fails  *
    *                      when no OMVS segment has been defined   *
    *                      for the userid of the I/O-Ops           *
    *                      application and RACF issues the message *
    *                      ICH408I. This message is repeatedly     *
    *                      issued since I/O-Ops retries to         *
    *                      establish the TCP connection on a       *
    *                      time-based method.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When no OMVS segment has been defined for the userid of the
    I/O-Ops application the message ICH408I is issued every time
    I/O-OPs tries to establish a TCP connection.
    

Problem conclusion

  • During start-up I/O-Ops checks the existence of the OMVS
    segment of the userid that is assigned to the started task. If
    the segment does not exist the message IHVI130I is issued and
    the TCP/IP communication is suppressed for the lifetime of the
    application.
    
    +------ System Automation for z/OS Version 3 Release 2 --------+
    |                                                              |
    |PROGRAM NUMBER: 5698-SA3                                      |
    |                                                              |
    |TITLE: System Automation for z/OS SC33-8264                   |
    |       Messages and Codes                                     |
    |                                                              |
    |CHAPTER: 8.0 Messages IHVA100I to IHVZ999I                    |
    |                                                              |
    |CHANGE:                                                       |
    |                                                              |
    | Add the following new message:                               |
    |                                                              |
    | IHVI130I OMVS segment of aa not found, SAF/RACF RC=bb/cc     |
    | RSN=dd.                                                      |
    |                                                              |
    | Explanation: I/O operations could not find an OMVS segment   |
    | that has been defined for its userid. Since some TCP/IP      |
    | macros require this segment the TCP/IP communication is      |
    | ignored for the lifetime of I/O operations.                  |
    |                                                              |
    |   The variable aa shows the userid of I/O operations.        |
    |                                                              |
    |   The variable bb shows the SAF return code of the           |
    |   RACROUTE EXTRACT request.                                  |
    |                                                              |
    |   The variable cc shows the RACF return code of the          |
    |   RACROUTE EXTRACT request.                                  |
    |                                                              |
    |   The variable dd shows the reason code of the               |
    |   RACROUTE EXTRACT request.                                  |
    |                                                              |
    | User response: If you want I/O operations to use TCP/IP      |
    | refer to "Customizing I/O Operations" in "System Automation  |
    | for z/OS: Planning and Installation" on how to define an     |
    | OMVS segment. After you have defined the OMVS segment you    |
    | need to restart I/O operations.                              |
    +--------------------------------------------------------------+
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA30756

  • Reported component name

    SYSTEM AUTO Z/O

  • Reported component ID

    5698SA300

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-10-14

  • Closed date

    2009-12-22

  • Last modified date

    2010-02-01

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

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

Modules/Macros

  • IHVIAEE  IHVICTA  IHVINI2  IHVXMSG
    

Publications Referenced
SC33826405        

Fix information

  • Fixed component name

    SYSTEM AUTO Z/O

  • Fixed component ID

    5698SA300

Applicable component levels

  • R320 PSY UA52019

       UP10/01/14 P F001

  • R322 PSY UA52020

       UP10/01/14 P F001

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli System Automation for z/OS

Software version:

320

Reference #:

OA30756

Modified date:

2010-02-01

Translate my page

Machine Translation

Content navigation