IFA707I SMF CANNOT CONNECT TO name REASON=text

Explanation

SMF encountered an error when connecting to the named log stream or in-memory resource using the IXGCONN service.

In the message text:
name
The log stream name or the in-memory resource name specified in SMFPRMxx or in a SETSMF command.
text
One of the following reasons:
  • LOGSTREAM NOT DEFINED
  • UNEXPECTED ERROR, rc - rsn
  • STAGING DATASET ERROR
  • BAD STRUCTURE NAME
  • LOGSTREAM DELETED
  • LOGSTREAM CONNECT LIMIT REACHED
  • BAD MODEL CONNECT
  • SYSTEM LOGGER IS NOT AVAILABLE
  • MAXIMUM WAIT OR RETRIES EXCEEDED, rc - rsn
  • DATA LOSS, rc - rsn
  • SAF RESOURCE WAS NOT DEFINED
  • TOO MANY IN-MEMORY RESOURCES DEFINED
  • THERE IS AN ACTIVE CONNECTION FOR THIS RESOURCE
See the system programmer response for descriptions of each reason.

System action

If the problem is resolved before SET SMF=xx or SETSMF processing completes, SMF automatically connects to the log stream.

If the problem was not resolved by the time SET SMF=xx or SETSMF processing completed and log stream recording was not activated, SMF continues with data set recording. If no MANx data sets are available, the SMF data is buffered until the buffer is full.

If log stream recording is in effect but SMF was not able to connect to the log stream, record types defined to be written to the log stream are written to the SMF buffer until the buffer is full.

Once the buffer is full, SMF data will be lost until the log stream becomes available or recording is switched to data set

Operator response

Contact the system programmer.

System programmer response

Issue the D SMF command to determine if the log stream connection was finally successful. If not, see the reason text to correct the problem. After that, issue the SET SMF=xx or the SETSMF command to establish the proper log stream recording environment again. If the problem with the log stream cannot be corrected, use the SET SMF=xx or the SETSMF command to ensure that all record types are designated to be written to available log streams, or switch to data set recording.
LOGSTREAM NOT DEFINED
Define the log stream (and corresponding coupling facility structure, if required) in the LOGR couple data set using the Administrative Data Utility (IXCMIAPU). See Setting up and managing SMF recording to logstreams in z/OS MVS System Management Facilities (SMF) and Planning for system logger applications in z/OS MVS Setting Up a Sysplex.
UNEXPECTED ERROR, rc - rsn
The IXGCONN service failed with reason and return code rc/rsn. See IXGCONN - Connect/disconnect to log stream in z/OS MVS Programming: Assembler Services Reference IAR-XCT to look up the IXGCONN return and reason code to determine the response to the problem.
STAGING DATASET ERROR
SMF will wait for notification (by the Event Notification Facility) that the log stream is ready and then will automatically try to use the log stream again.
BAD STRUCTURE NAME
The coupling facility structure name, defined for the log stream, is not correct. If the structure was not defined, use IXCMIAPU to define it in the CFRM couple data set. If the structure name is incorrect for the log stream definition in the LOGR couple data set, correct it in LOGR using IXCMIAPU. See Administrative data utility in z/OS MVS Setting Up a Sysplex.
LOGSTREAM DELETED
The log stream that SMF is connecting to is in the process of being deleted. Specify a new log stream name in the SMFPRMxx parmlib member.
LOGSTREAM CONNECT LIMIT REACHED
The system has reached the limit for the maximum number of log streams that can be concurrently active. An MVS™ image may connect to a maximum of 4096 log streams concurrently. Either plan your workload to either consolidate log streams or balance system activity so that fewer log streams are needed in a given time period.
BAD MODEL CONNECT
The log stream specified in the SMFPRMxx parmlib member was defined in the LOGR couple data set as a model log stream (MODEL=YES). A model log stream is just for use as a model for other log stream definitions on the LIKE parameter. Change the log stream name in SMFPRMxx to one that is not defined as a model.
SYSTEM LOGGER IS NOT AVAILABLE
Either the system logger address space is not active, or it is not accepting requests for system logger services at this time.
MAXIMUM WAIT OR RETRIES EXCEEDED, rc - rsn
The IXGCONN service failed with reason and return code rc-rsn. After waiting for the problem to be resolved, SMF retried the operation but the error persisted. For more information about the problem, see IXGCONN return and reason codes in z/OS MVS Programming: Assembler Services Reference IAR-XCT to find the IXGCONN return and reason code.
DATA LOSS, rc - rsn
The IXGCONN service failed with reason and return code rc - rsn. This indicates that there may be log blocks permanently missing from the logstream. This is an unacceptable condition for SMF data recording. SMF disconnected from the logstream so the logstream can be repaired. To recover from this condition, the IXCMIAPU LOGR utility can be used to rename the failing log stream. IXGINVNT or IXCMIAPU can then be used to define a new log stream with the old name. In this way, the existing logstream name can be used to start logging again. When the logstream is available again, issue the SET SMF=xx command to reinstate SMF recording to the logstream. The IFASEXIT SMF exit can be used to dump the data from the logstream that is in the "data loss" state.
SAF RESOURCE WAS NOT DEFINED
There is no SAF resource defined to correspond to the in-memory resource. Define the SAF resource as instructed in z/OS MVS Initialization and Tuning Reference.
TOO MANY IN-MEMORY RESOURCES DEFINED
The maximum allowed number of in-memory resources has already been reached. No additional in-memory resources can be defined.
THERE IS AN ACTIVE CONNECTION FOR THIS RESOURCE
An attempt was made to change the in-memory resource while there is still an active connection. Ensure that all users are disconnected, then attempt the change again.

Source

SMF

Module

IFALSMOD

Routing code

*,2,10

Descriptor code

4,5