12/16
8 Network Messages
This chapter describes the messages that are issued by the Oracle Network Service on z/OS. Error and warning messages are written to the system console. Informational messages are generally only written to the Oracle NETLOG DD.
The messages all begin with the prefix "MIN" followed by a 4-digit decimal number followed by a letter to identify the action and severity associated with each message. The final letter indicates one of the following:
The network messages are often created with character substitutions. In the messages below,%x represents some hexadecimal value, %d a decimal value, and %c a character value. The number of x's, d's, and c's after the % represent the precision of the expected value with the %
counting as 1. For example %cccc means that a character value substitution with a length of five is expected.
To find the return code values for TCP/IP failures, refer to the IBM manual Communications Server IP and SNA Codes or its equivalent for the level of z/OS.
The following messages are described in this chapter:
8.1 Messages MIN0001I to MIN1105E
- MIN0001I networking service initializing
-
Cause: This message is a normal Oracle Net start up message.
-
Action: No action is required.
- MIN0002I networking service %ccccccc initialization complete
-
Cause: This message is a normal Oracle Net start up message.
-
Action: No action is required.
- MIN0003E module MINMAIN is not in an APF-authorized library
-
Cause: Oracle Net must be executed from an APF authorized library.
-
Action: Authorize the library and restart Oracle Net.
- MIN0004E unable to obtain storage for global vector
-
Cause: Not enough virtual storage is available to Oracle Net.
-
Action: Increase the Oracle Net region and restart.
- MIN0005I global vector is at %xxxxxxx
-
Cause: This message is a normal Oracle Net start up message.
-
Action: No action is required.
- MIN0006E failure executing ASEXT, R15 = %d, R0 = %d
-
Cause: This message is a critical error. Oracle Net will not function properly.
-
Action: The information displayed in the message should be reported to Oracle Support Services.
- MIN0008E unable to obtain %dddd bytes of storage for %ccccccc
-
Cause: Insufficient storage space is available.
-
Action: Increase the Oracle Net region and restart.
- MIN0009E unable to obtain %dddd bytes of %ccc for %ccccccc, rc = %d
-
Cause: Insufficient storage space is available.
-
Action: Increase the Oracle Net region and restart.
- MIN0010E unable to attach subtask %ccccccc, ATTACH RC = %ddd
-
Cause: This message is a critical error. Oracle Net will not function properly.
-
Action: The information displayed in the message should be reported to Oracle Support Services.
- MIN0011E subtask %ccccccc abended with S%xx/U%ddd during initialization.
-
Cause: This message is a critical error. Oracle Net will not function properly.
-
Action: The information displayed in the message should be reported to Oracle Support Services.
- MIN0012E Invalid reply area on %ccccccc to subsystem %ccc
-
Cause: This message is a critical error. Oracle Net will not function properly.
-
Action: The information displayed in the message should be reported to Oracle Support Services.
- MIN0013E signon to subsystem %ccc rejected, RC = %ddd
-
Cause: This message is a critical error. Oracle Net will not function properly.
-
Action: The information displayed in the message should be reported to Oracle Support Services.
- MIN0014E signon to subsystem %ccc failed, RC = %ddd, RSN = %ddd, INFO = %ddd
-
Cause: This message is a critical error. Oracle Net will not function properly.
-
Action: The information displayed in the message should be reported to Oracle Support Services.
- MIN0016I command service subtask initialized
-
Cause: This message is a normal Oracle Net start up message
-
Action: No action is required.
- MIN0017I message service subtask initialized
-
Cause: This message is a normal Oracle Net start up message
-
Action: No action is required.
- MIN0018I bind/unbind service subtask initialized
-
Cause: This message is a normal Oracle Net start up message
-
Action: No action is required.
- MIN0019W multiple TCP/IP tasks requested, none will be started
-
Cause: Only one TCP/IP protocol task may be active within Oracle Net.
-
Action: Correct the OSDI Oracle Net start parms.
- MIN0020W Internal tracing will not be performed
-
Cause: There was not enough storage available for the internal trace table.
-
Action: This message is not a fatal error, but the Oracle Net region should be increased and Oracle Net restarted.
- MIN0021E unable to start networking task, storage unavailable
-
Cause: Storage is unavailable.
-
Action: Increase the Oracle Net region and restart.
- MIN0022W Invalid service parameter %ccccccc ignored
-
Cause: The parameter shown from the service definition or alter is not recognized.
-
Action: This message may indicate that Oracle Net was started with a JES start command rather than an OSDI subsystem start command. The latter must be used.
- MIN0023W Invalid service parameter beginning with %ccccccc, ignored
-
Cause: The parameter shown from the service definition or alter is not recognized.
-
Action: This message may indicate that Oracle Net was started with a JES start command rather than an OSDI subsystem start command. The latter must be used.
- MIN0024I connected to WLM subsystem %cccc
-
Cause: This message is a normal Oracle Net start up message.
-
Action: No action is required.
- MIN0025W WLM not active, connect failed RC=%xxxx RSN=%xxxxxxxx
-
Cause: Oracle Net will continue, but work will be scheduled into the Oracle server on preemptable SRB's instead of enclave SRB's and the work will not be managed by WLM.
-
Action: Activate WLM if you want to have it manage the work scheduled for the Oracle server.
- MIN0026I timer service subtask initialized
-
Cause: This message is a normal Oracle Net start up message.
-
Action: No action is required.
- MIN0027I session/transaction enclave duration
-
Cause: This message indicates the enclave duration for WLM services.
-
Action: No action is required.
- MIN0091I timer service subtask terminated
-
Cause: This message is a normal Oracle Net start up message.
-
Action: No action is required.
- MIN0092W WLM disconnect failed RC=%xxxx RSN=%xxxxxxxx
-
Cause: Oracle Net will continue to terminate, but a graceful termination of WLM services was not possible.
-
Action: None, Oracle Net will continue shutdown.
- MIN0093I command service subtask terminated
-
Cause: This message is a normal Oracle Net termination message.
-
Action: No action is required.
- MIN0094I message service subtask terminated
-
Cause: This message is a normal Oracle Net termination message.
-
Action: No action is required.
- MIN0095I bind/unbind service subtask terminated
-
Cause: This message is a normal Oracle Net termination message.
-
Action: No action is required.
- MIN0096E signoff from subsystem %ccc rejected, RC = %ddd
-
Cause: Oracle Net has been stopped but cannot properly remove itself from the OSDI subsystem.
-
Action: This message should be reported to Oracle Support Services.
- MIN0097E signoff from subsystem %ccc failed, RC = %ddd, RSN = %ddd, INFO = %ddd
-
Cause: Oracle Net has been stopped but cannot properly remove itself from the OSDI subsystem.
-
Action: This message should be reported to Oracle Support Services.
- MIN0098I networking service %ccccccc termination in progress
-
Cause: This message is a normal Oracle Net termination message.
-
Action: No action is required.
- MIN0099I networking service termination complete
-
Cause: This message is a normal Oracle Net termination message.
-
Action: No action is required.
- MIN0100W command ignored, shutdown in progress
-
Cause: Modify commands cannot be processed once Oracle Net receives a stop command. It may take several minutes for Oracle Net to shut down after the stop command has been received.
-
Action: Allow Oracle Net to continue its shutdown. Do not try to enter more commands.
- MIN0101I task %ccccccc already active, START command ignored
-
Cause: A modify command is trying to start a protocol that is already active.
-
Action: No action is required.
- MIN0102I task %ccccccc not active, STOP command ignored
-
Cause: A modify command is trying to stop a protocol that is not yet active.
-
Action: No action is required.
- MIN0103E unrecognized command verb
-
Cause: A modify command has been entered, but it does not specify one of the support action verbs.
-
Action: Enter a corrected command.
- MIN0104E unrecognized keyword in command
-
Cause: A modify command has been entered, but it does not specify a supported keyword for the provided verb.
-
Action: Enter a corrected command.
- MIN0105E unrecognized OSDI command %d
-
Cause: An OSDI command has been entered, but it does not specify an action verb supported by Oracle Net.
-
Action: Enter a corrected command.
- MIN0106E error retrieving OSDI command, RC = %d
-
Cause: An OSDI command has been entered for Oracle Net, but Oracle Net was unable to retrieve the actual command.
-
Action: Report this error to Oracle Support Services.
- MIN0107E TCP/IP subtask %ccccccc already active, START command ignored
-
Cause: An attempt was made to start a second TCP/IP protocol task. This is not allowed.
-
Action: Stop the active protocol task before attempting another start.
- MIN0108E Resource error while attempting display command.
-
Cause: A request was made to display the current active protocol connections, but resources are not available to do so without interfering with activity on those connections.
-
Action: Attempt the command again. If the error persists, contact Oracle Support Services.
- MIN0200I CID Owner Protocol Address
-
Cause: This message is used to respond to a Oracle Net 'modify dis' (display) command to show active connections.
-
Action: No action is required.
- MIN0201I
%xxxxxxx %ccccccc
TCP %cccccccccccccc/%dddd
-
Cause: This message is used to respond to a Oracle Net 'modify dis' (display) command to show active connections
-
Action: No action is required.
- MIN0203I %ccccccc has %d Sub-tasks active, %d are protocol tasks , GV is at %xxxxxxx.
-
Cause: This message is used to respond to an OSDI 'DISPLAY name,L' command to show status.
-
Action: No action is required.
- MIN0204I SubTask Protocol @TCB Terminated?
-
Cause: This message is used to respond to an OSDI 'DISPLAY name,L' command to show status of an OSDI Net service.
-
Action: No action is required.
- MIN0205I %ccccccc %ccc %xxxxxxx %cc
-
Cause: This message is used to respond to an OSDI 'DISPLAY name,L' command to show status.
-
Action: No action is required.
- MIN0206I Pool SP Size Free Total Reuses
-
Cause: This message is used to respond to a Oracle Net 'modify dis pool' command to show storage use.
-
Action: No action is required.
- MIN0207I %CCC %dd %dddd %ddddddddd %ddddddddd %ddddddddd
-
Cause: This message is used to respond to a Oracle Net 'modify dis pool' command to show storage use.
-
Action: No action is required.
- MIN0300E memory unavailable for new %ccc pool element
-
Cause: Oracle Net is short on storage. It will continue to operate, but may be unable to handle new work.
-
Action: Increase the Oracle Net region and restart.
- MIN0303E unable to locate CBX for CID %xxxxxxx
-
Cause: Oracle Net has probably suffered corruption of control structures.
-
Action: A console dump of the address space should be taken, and Oracle Net restarted as soon as practical.
- MIN0304S Internal error, CB and CBX specify different CIDs
-
Cause: Oracle Net has probably suffered corruption of control structures.
-
Action: A console dump of the address space should be taken, and Oracle Net restarted as soon as practical.
- MIN0305E unable to obtain buffer of size %dddd
-
Cause: Oracle Net is short on storage. It will continue to operate, but may be unable to handle new work.
-
Action: Increase the Oracle Net region an restart.
- MIN0306E bind request to subsystem %ccc rejected with RC = %d
-
Cause: A server to which a remote client is trying to connect is not available.
-
Action: Check the system log for 'MIS' messages to help determine why. If the reason for failure is not apparent, contact Oracle Support Services with the information for all MIN and MIS messages.
- MIN0307E bind to service %ccccccc failed, RC = %d, RSN = %ddd, I NFO = %ddd
-
Cause: A server to which a remote client is trying to connect is not available.
-
Action: Check the system log for 'MIS' messages to help determine way. If the reason for failure is not apparent, contact Oracle Support Services with the information from all MIN and MIS messages.
- MIN0308E unbind request to subsystem
%ccc
rejected with RC = %d
-
Cause: A server from which a remote client is trying to disconnect is not responding correctly.
-
Action: Check the system log for 'MIS' messages to help determine way. If the reason for failure is not apparent, contact Oracle Support Services with the information from all MIN and MIS messages. The protocol side of the connection will be terminated.
- MIN0309E unbind to service %ccccccc failed, RC = %d, RSN = %ddd, INFO = %ddd
-
Cause: A server from which a remote client is trying to disconnect is not responding correctly.
-
Action: Check the system log for 'MIS' messages to help determine why. If the reason for failure is not apparent, contact Oracle Support Services with the information from all MIN and MIS messages. The protocol side of the connection will be terminated.
- MIN0310W WLM enclave create failed RC=%xxxx RSN=%xxxxxxxx protocol %ccc.
-
Cause: This message may be due to IBM imposed restrictions on the number of enclaves that may be created by a single address space.
-
Action: Oracle Net will continue, but work will be scheduled into the Oracle server for this connection on a preemptable SRB instead of an enclave SRB and the work will not be managed by WLM.
- MIN0311W WLM enclave delete failed RC=%xxxx RSN=%xxxxxxxx protocol %ccc.
-
Cause: Oracle Net was not able to delete an enclave, probably because a SRB was active when a client tried to force a disconnection.
-
Action: Processing will continue and the connection will be dropped.
- MIN0700I HPNS INITAPI call performed. RC=
%ddd
, EC=%dddd
-
Cause: If the RC and EC are anything other than 0, then Oracle Net TCP/IP protocol will not function correctly. The RC and EC are return code and error number from an EZASMI TYPE=INITAPI macro call.
-
Action: Refer to the IBM manual Communications Server IP and SNA Codes for an explanation of what the error number is from this EZASMI macro call. Generally this message indicates that there is a configuration error and the error number gives some indication of what that error is.
- MIN0701E getclientid failed invoke. RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol cannot initialize correctly and will not function correctly. The RC and EC are return code and error number from an EZASMI TYPE=GETCLIENTID macro call.
-
Action: Refer to the IBM manual Communications Server IP and SNA Codes for an explanation of what the error number is from this EZASMI macro call. Generally this message indicates that there is a configuration error. It should be reported to Oracle Support Services for assistance in determining the cause.
- MIN0702E getclientid call failed. RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol cannot initialize correctly and will not function correctly. The RC and EC are return code and error number from the completion of an EZASMI TYPE=GETCLIENTID macro call.
-
Action: Refer to the IBM manual Communications Server IP and SNA Codes for an explanation of what the error number is from this EZASMI macro call. Generally this message indicates that there is a configuration error. It should be reported to Oracle Support Services for assistance in determining the cause.
- MIN0703E gethostid failed invoke. RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol cannot obtain the default home internet address and will terminate. The RC and EC are return code and error number from an EZASMI TYPE=GETHOSTID macro call.
-
Action: Refer to the IBM manual Communications Server IP and SNA Codes for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0704E gethostid failed invoke. RC=%ddd
-
Cause: The Oracle Net TCP/IP protocol cannot obtain the default home internet address and will terminate. The RC and EC are return code and error number from the completion of an EZASMI TYPE=GETHOSTID macro call.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0705E gethostbyname attach failed. RC=%ddd
-
Cause: The Oracle Net TCP/IP protocol cannot attach the gethostbyname task and will terminate. The return code is the return code from an ATTACHX macro call.
-
Action: This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0706E Attach of HPNS kid task failed. RC=%ddd
-
Cause: The Oracle Net TCP/IP protocol cannot attach a kid task and will terminate. The return code is the return code from an ATTACHX macro call.
-
Action: This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0707E listen-socket failed invoke. RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol cannot obtain a socket descriptor from TCPIP and will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=SOCKET macro call.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0708E listen-socket call failed. RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol cannot obtain a socket descriptor from TCPIP and will terminate. The RC and EC are return code and error number from the completion from an EZASMI TYPE=SOCKET macro call.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0709E bind socket failed invoke. RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol cannot bind to a port in TCPIP and will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=BIND macro call.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0710E bind socket call failed. RC=%ddd, EC=%dddd
-
Cause: The TCP/IP protocol cannot initialize correctly.
-
Action: Report this message to Oracle Support Services
- MIN0711E listen failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The TCP/IP protocol cannot initialize correctly.
-
Action: Report this message to Oracle Support Services
- MIN0712E listen call failed. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol cannot listen on a port in TCPIP and will terminate. The RC and EC are return code and error number from the completion from an EZASMI TYPE=LISTEN macro call.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0713I I am listening on port %dddd socket %dddd
-
Cause: This message is normal and indicates that Oracle Net is listening on port nnnn and will accept connection request on this port.
-
Action: None.
- MIN0714E accept failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol issued an accept connection request which failed and Oracle Net will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=ACCEPT macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0715W accept call failed. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol issued an accept connection request which failed to complete. Oracle Net attempts to correct this and will continue as far as it can. If it cannot correct the error then Oracle Net will terminate. The RC and EC are return code and error number from the completion from an EZASMI TYPE=ACCEPT macro call.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is possibly a network error. This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0716E givesocket failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol issued a givesocket to hand off a connection to a Oracle Net kid. Oracle Net will continue; however, probably with reduced functionality. The RC and EC are return code and error number from the call to an EZASMI TYPE=GIVESOCKET macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is possibly a network or a configuration error (for example; not enough sockets defined). This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0717E givesocket call failed. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol issued an givesocket to hand off a connection to an Oracle Net kid which failed to complete. Oracle Net will continue; however, with reduced functionality. The RC and EC are return code and error number from the completion from an EZASMI TYPE=GIVESOCKET macro call.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is possibly a network or a configuration error (for example; not enough sockets defined). This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0718E close for given failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol issued an close socket to close a connection which failed. Oracle Net will continue. The RC and EC are return code and error number from the call to an EZASMI TYPE=CLOSE macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0719W close for given call failed. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol issued an close socket to close a connection which failed to complete. Oracle Net will continue. The RC and EC are return code and error number from the completion from an EZASMI TYPE=CLOSE macro call.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message should be reported to Oracle Support Services for assistance in determining the cause.
- MIN0721I HPNS shut down, GoodBye.
-
Cause: This message is normal and indicates that the Oracle Net TCP/IP protocol has shutdown.
-
Action: None
- MIN0722I HPNS Kid #%dd shut down.
-
Cause: This message is normal and indicates that one of the kid slaves has shutdown.
-
Action: None
- MIN0723I HPNS Gethostbyname subtask ended.
-
Cause: This message is normal and indicates that the Oracle Net gethostbyname subtask has shutdown.
-
Action: None
- MIN0724I HPNS GHBY INITAPI call performed. RC=%ddd, EC=%dddd
-
Cause: If the RC and EC are anything other than 0 then Oracle Net TCP/IP protocol will not function correctly. This subtask performs all the name resolution for IP addresses (DNS). The RC and EC are return code and error number from an EZASMI TYPE=INITAPI macro call.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance if the return code and error number is anything other than 0.
- MIN0725E gethostname failed invoke. RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol cannot obtain the default host name and will terminate. The RC and EC are return code and error number from a call to an EZASMI TYPE=GETHOSTNAME macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. It can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0726E gethostname failed invoke. RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol cannot obtain the default host name and will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=GETHOSTNAME macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. It can be reported to Oracle Support Services for assistance in determining the cause.
- MIN0727E gethostbyname call failed. RC=%ddd
-
Cause: The Oracle Net TCP/IP protocol cannot obtain the resolve the default host name obtained from the gethostname call and thus fails to initialize and will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=GETHOSTBYNAME macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. It can be reported to Oracle Support Services for assistance in determining the cause. This may also indicate that IBM Language Environment is not available.
- MIN0728I HPNS KID INITAPI call performed. RC=%ddd, EC=%dddd
-
Cause: If the RC and EC are anything other than 0 then Oracle Net TCP/IP protocol will not function correctly. This subtask performs all the work for IP connections and multiple subtasks (kids) are started. The RC and EC are return code and error number from an EZASMI TYPE=INITAPI macro call.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance if the return code and error number is anything other than 0.
- MIN0729E KID getclientid failed invoke. RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol issued an getclientid to initialize a Oracle Net kid which failed. Oracle Net will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=GETCLIENTID macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.
- MIN0730E KID getclientid call failed. RC=%ddd, EC=%dddd
-
Cause: The Oracle Net TCP/IP protocol issued an getclientid to initialize a Oracle Net kid which failed to complete. Oracle Net will terminate. The RC and EC are return code and error number from the completion of the call to an EZASMI TYPE=GETCLIENTID macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.
- MIN0731E takesocket failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The setup of a TCP/IP connection has failed. The kid is trying to take connection request and has failed. Oracle Net will try to continue. The RC and EC are return code and error number from the call to an EZASMI TYPE=TAKESOCKET macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.
- MIN0732E takesocket call failed. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The setup of a TCP/IP connection has failed. The kid is trying to take connection request and has failed. Oracle Net will try to continue. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=TAKESOCKET macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.
- MIN0733I Socket %ddd connected Subtask %ccc, IP %cccccccccccccc, Port %dddd.
-
Cause: This message is a normal TCP/IP connection message for an inbound connection request to a z/OS server from some remove TCP/IP client.
-
Action: None.
- MIN0734E setsocket failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The setup of a TCP/IP connection has failed. The kid is trying to set up the connection and has failed. Oracle Net will try to continue. The RC and EC are return code and error number from the call to an EZASMI TYPE=SETSOCKOPT macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.
- MIN0735E setsocket call failed. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: The setup of a TCP/IP connection has failed. The kid is trying to set up the connection and has failed. Oracle Net will try to continue. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=SETSOCKOPT macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.
- MIN0736E receive failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd
-
Cause: A TCP/IP connection has failed. The kid is trying to receive some data and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=RECV macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to a network error.
- MIN0737E receive call failed. Sckt=%dddd RC=
%ddd
, EC=%dddd
-
Cause: A TCP/IP connection has failed. The kid is trying to receive some data and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=RECV macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to a network error.
- MIN0738E send failed invoke. Sckt=
%dddd
RC=%ddd, EC=%dddd
-
Cause: A TCP/IP connection has failed. The kid is trying to send some data and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=SEND macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance however, any error is most likely to be due to a network error.
- MIN0739E send call failed. Sckt=
%dddd
RC=%ddd
, EC=%dddd
-
Cause: A TCP/IP connection has failed. The kid is trying to send some data and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=SEND macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to a network error.
- MIN0740E close failed invoke. Sckt=
%dddd
RC=%ddd
, EC=%dddd
-
Cause: A TCP/IP connection has failed. The kid is trying to close a connection and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=CLOSE macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to a network error.
- MIN0741E close call failed. Sckt=
%dddd
RC=%ddd
, EC=%dddd
-
Cause: A TCP/IP connection has failed. The kid is trying to close a connection and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=CLOSE macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to a network error.
- MIN0742I Socket
%ddd
closed Subtask %ccc
, IP %cccccccccccccc
, Port %dddd
.
-
Cause: This message is normal and indicates that a remote TCP/IP connection has closed.
-
Action: None
- MIN0743E socket failed invoke. Sckt=
%dddd
RC=%ddd
, EC=%dddd
-
Cause: The Oracle Net TCP/IP connection cannot obtain a socket descriptor from TCPIP. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=SOCKET macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.
- MIN0744E socket call failed. Subtask
%ccc
RC=%ddd
, EC=%dddd
-
Cause: The Oracle Net TCP/IP connection cannot obtain a socket descriptor from TCPIP. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=SOCKET macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.
- MIN0745E connect failed invoke. Subtask
%ccc
Sckt=%ddd
, RC=%ddd
, EC=%dddd
-
Cause: The local client cannot establish a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=CONNECT macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.
- MIN0746E connect call failed. Subtask
%ccc
Sckt=%ddd
, RC=%ddd
, EC=%dddd
-
Cause: The local client cannot establish a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=CONNECT macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.
- MIN0747E getsockname failed invoke. Subtask
%ccc
Sckt=%ddd
, RC=%ddd
, EC=%dddd
-
Cause: The local client cannot establish a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=GETSOCKNAME macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.
- MIN0748E getsockname call failed. Subtask
%ccc
Sckt=%ddd
, RC=%ddd
, EC=%dddd
-
Cause: The local client cannot establish a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=GETSOCKNAME macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.
- MIN0749I Socket %ddd connected Subtask
%ccc
, IP %cccccccccccccc
, Port %dddd
.
-
Cause: This message is a normal message issued when an outbound z/OS client connects to a remote server through TCP/IP.
-
Action: None.
- MIN0750E cancel recv failed invoke. Subtask
%ccc
Sckt=%ddd
, RC=%ddd
, EC=%dddd
-
Cause: The local client cannot close a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=CANCEL macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.
- MIN0751E cancel recv call failed. Subtask
%ccc
Sckt=%ddd
, RC=%ddd
, EC=%dddd
-
Cause: The local client cannot close a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=CANCEL macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.
- MIN0752E cancel accept failed invoke. Subtask
%ccc
Sckt=%ddd
, RC=%ddd
, EC=%dddd
-
Cause: The local socket cannot close a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=CANCEL macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.
- MIN0753E cancel accept call failed. Subtask
%ccc
Sckt=%ddd
, RC=%ddd
, EC=%dddd
-
Cause: The local socket cannot close a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion to a call to an EZASMI TYPE=CANCEL macro.
-
Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.
- MIN0901S diagnostic dump failed for abend S
sss
/Uuuuu
, SDUMPX RC = rc
, RSN = rs
-
Cause: The SDUMPX macro has failed to complete for the system ABEND sss or the user ABEND uuuu.
-
Action: Refer to the IBM manual MVS Programming: Authorized Assembler Services Reference, Vol. 2 for further information about macro SDUMPX, return code rc, reason code rs, and appropriate actions.
- MIN0900W diagnostic dump suppressed for abend S%xx/U%ddd
-
Cause: The dump was suppressed for system ABEND sss or the user ABEND uuuu.
-
- MIN0901S diagnostic dump failed for abend S
sss
/Uuuuu
, SDUMPX RC = rc
, RSN = rs
-
Cause: The SDUMPX macro has failed to complete for the system ABEND sss or the user ABEND uuuu.
-
Action: Refer to the macro SDUMPX in the IBM manual MVS Programming: Authorized Assembler Services Reference, Vol. 2 for further information about return code rc and reason code rs and appropriate actions.
- MIN0902S loop in %ccc freepool element %xxxxxxx, some memory now unusable
-
Cause: A loop was detected in the free memory chain.
-
Action: A console dump of the address space should be taken, and Oracle Net restarted as soon as practical.
- MIN0903S overlay in %ccc freepool element %xxxxxxx, some memory now unusable
-
Cause: An overlay was detected in the free memory chain.
-
Action: A console dump of the address space should be taken, and Oracle Net restarted as soon as practical.
- MIN0904S message %dddd not found in message table'
-
Cause: The message is not in the message table.
-
Action: The information displayed in the message should be reported to Oracle Support Services.
- MIN0905E internal error in %ccccccc, unrecognized AR type %d received
-
Cause: The net AR type is not recognized.
-
Action: The information displayed in the message should be reported to Oracle Support Services.
- MIN0906E internal error in %ccccccc, unrecognized request option %d in AR type %d
-
Cause: The option for the net AR type is not recognized.
-
Action: The information displayed in the message should be reported to Oracle Support Services.
- MIN0907E internal error in %ccccccc, no matching task block found
-
Cause: The TB control block cannot be found.
-
Action: A console dump of the address space should be taken, and Oracle Net restarted as soon as practical.
- MIN0908I SRB abend PSW=%xxxxxxxx %xxxxxxxx CODE=%xxxxxxxx REAS=%xxxxxxxx
-
Cause: The SRB has abended
-
Action: Refer to the MVS System Codes or the User Abend Codes section of this manual for further information.
- MIN1100E request rejected, shutdown in progress
-
Cause: The Net address space is terminating the request is rejected
-
Action: Restart the net address space.
- MIN1101E unable to obtain %dd bytes of memory for API request
-
Cause: Oracle Net is short on storage. It will continue to operate, but may be unable to handle new work.
-
Action: Increase the Oracle Net region and restart.
- MIN1102E unable to obtain %dddd bytes of memory for data buffer
-
Cause: Oracle Net is short on storage. It will continue to operate, but may be unable to handle new work.
-
Action: Increase the Oracle Net region and restart.
- MIN1103E request rejected, CID is no longer valid
-
Cause: The connection id cannot be located.
-
Action: If the problem persists, a console dump of the address space should be taken and the problem reported to Oracle Support Services.
- MIN1104E request rejected, unable to locate connection block
-
Cause: The connection is marked idle.
-
Action: If the problem persists, a console dump of the address space should be taken and the problem reported to Oracle Support Services.
- MIN1105E request rejected, invalid AR type %d
-
Cause: The net AR type is not recognized.
-
Action: The information displayed in the message should be reported to Oracle Support Services.