Action: None.

Meaning: IXCJOIN completed successfully; the member is the first active member of the group. XCF places member information in ANSAREA.

Action: None required.

Meaning: IXCJOIN completed successfully; the member already exists in a failed state, and the caller correctly specified LASTING=YES. A new member token has been assigned to the new instance of the member.

Action: None required. However, because the previous instance of the member was in a failed state, your application might need to perform some type of cleanup or takeover processing. MVS™ placed the member in the failed state when the member's corresponding task, address space, or system terminated. If the user state of the previous instance is needed and you must specify a user state on the IXCJOIN request, you can change your program to issue an IXCQUERY prior to the IXCJOIN to capture the user state of the previous instance. If you do not specify a user state on IXCJOIN, the new instance of the member will retain the user state of the old instance.

Meaning: IXCJOIN completed successfully; the member already exists in a quiesced state, and the caller correctly specified LASTING=YES. A new member token has been assigned to the new instance of the member.

Action: None required. However, because the previous instance of the member was in a quiesced state, your application might need to perform some type of cleanup or takeover processing. The previous instance of the member voluntarily placed itself in a quiesced state. If the user state of the previous instance is needed and you must specify a user state on the IXCJOIN request, you can change your program to issue an IXCQUERY prior to the IXCJOIN to capture the user state of the previous instance. If you do not specify a user state on IXCJOIN, the new instance of the member will retain the user state of the old instance.

Meaning: IXCJOIN completed successfully. The member already exists in a created state, and the caller correctly specified LASTING=YES.

Action: None required. However, you might take some action based on your application. You can use the member's current user state to determine what action needs to be taken.

Meaning: Program error. The member already exists in a created state, and the caller did not specify LASTING=YES. LASTING=YES must be specified since the member already has permanent status recording. The member's state and user state are not altered.

Action: Ensure that your program specifies LASTING=YES, and retry the request. If permanent status recording is not required for this instance of the member, issue IXCDELET to delete the member, and retry the IXCJOIN request.

Meaning: Program error. The member already exists in an active state.

Action: None required. However, you might take some action depending on your application.

Meaning: Program error. The member already exists in a quiesced state, and the caller did not specify LASTING=YES. LASTING=YES must be specified since the member already has permanent status recording. The member's state and user state are not altered.

Action: Ensure that your program specifies LASTING=YES, and retry the request. If permanent status recording is not required for this instance of the member, issue IXCDELET to delete the member, and retry the IXCJOIN request. Before you delete the member, you can use the IXCQUERY service to capture the member's current user state.

Meaning: Program error. The member already exists in a failed state, and the caller did not specify LASTING=YES.

Action: Ensure that your program specifies LASTING=YES, and retry the request. If permanent status recording is not required for this instance of the member, issue IXCDELET to delete the member, and retry the IXCJOIN request. Prior to deleting the member, you can use the IXCQUERY service to capture the member's current user state.

Meaning: Program error. The group name is not valid.

Action: Correct the group name, and retry the request.

Meaning: Program error. The member name is not valid.

Action: Correct the member name, and retry the request.

Meaning: Program error. The status-checking interval value is zero or is not a multiple of 100.

Action: Correct the status-checking interval, and retry the request.

Meaning: Program error. XCF could not access the STATFLD.

Action: Ensure that the STATFLD parameter is correct. The STATFLD must be a doubleword in fixed or DREF common storage.

Meaning: Program error. The caller specified LASTING=YES without specifying the member name. XCF will not generate member names for members that have permanent status recording.

Action: If the member requires permanent status recording, provide a member name. If the member does not require permanent status recording, do not specify LASTING=YES.

Meaning: Program error. The STATFLD, INTERVAL, or STATEXIT parameter is missing. For XCF to monitor the member's status, all three of these values must be specified.

Action: Ensure that the STATFLD, INTERVAL, and STATEXIT are correct, and retry the request.

Meaning: Program error. The caller specified ANSAREA or ANSLEN incorrectly. Even though the member might have been placed in an active state, the ANSAREA was nonaddressable or the ANSLEN was not large enough.

Action: Check the two high-order bytes of this reason code fullword xxyy003C for the return code xx (either 00 or 04) and reason code yy the caller would have received from IXCJOIN if the caller had coded those parameters correctly. Take action as described by the corresponding return and reason code. You might want to abnormally end your program or take some other action that will record the problem. You should correct your program to ensure that the ANSAREA is addressable and that the ANSLEN is large enough. See the description of these keywords for their requirements.

If the return and reason code indicate that the member was placed in an active state, you can use the IXCQUERY service to get the information that would have been returned in the ANSAREA.

Meaning: Program error or environmental error. A reserved field in the control parameter list is not zero.

Action: Check to see if your program inadvertently overlaid the parameter list storage, and that it was assembled with the correct macro library for the release of MVS your program is running on.

Meaning: Program error. The member association value (task, address space or job) is not correct in the parameter list.

Action: Check to see if your program inadvertently overlaid the parameter list storage, and that it was assembled with the correct macro library for the release of MVS your program is running on.

Meaning: Program error. Your program is not running in primary ASC mode, and the ALET that qualifies the address of the control parameter list is neither zero nor associated with a valid public entry on the caller's DU-AL.

Meaning: Program error or environmental error. The version number in the control parameter list is not valid.

Action: Check to see if your program inadvertently overlaid the parameter list storage, and that it was assembled with the correct macro library for the release of MVS your program is running on.

Meaning: Program error or environmental error. The function code in the control parameter list is not valid.

Action: Check to see if your program inadvertently overlaid the parameter list storage, and that it was assembled with the correct macro library for the release of MVS your program is running on.

Meaning: Program error. XCF could not access the control parameter list.

Meaning: Program error. XCF could not access the USTATE value.

Meaning: Program error. The USLEN value is less than 1 or greater than 32.

Action: Correct the USLEN, and retry the request.

Meaning: Program error. The caller is not in task mode.

Action: Correct your program so that it issues IXCJOIN only while in task mode.

Meaning: The caller is not enabled.

Action: Correct your program so that it does not issue IXCJOIN while it is disabled.

Meaning: Program error. The primary address space is not equal to the home address space.

Action: Correct your program so that it does not use IXCJOIN while in cross memory mode. You might want to pass this restriction on to your caller when you are unsure of the environment in which your caller may call your program.

Meaning: Program error. XCF does not allow the JOIN process during or after task termination.

Action: Correct your program so that it does not issue IXCJOIN from a task that is terminating. Ensure that your application does not invoke IXCJOIN from a task termination resource manager. You might want to pass this restriction on to your caller when you are unsure of the environment in which your caller may call you.

Meaning: Program error. The FUNCTION keyword does not specify a valid descriptor (bad character, leading blanks, all blank).

Action: Correct the FUNCTION specification.

Meaning: Environmental error. The maximum number of groups already exists.

Action: Retry the request at least once. If the problem persists, consult your system programmer to determine if the number of groups defined in the couple data set should be increased, or if the XCF limit on the number of groups has been reached. Your application should cover cases in which the couple dataset has no available room. Before running or installing your application, you should make the system programmer aware of your XCF group and member resource requirements.

Meaning: Environmental error. The maximum number of members in the group already exists.

Action: Retry the request at least once. If the problem persists, consult your system programmer to determine if the maximum number of members defined in the couple data set should be increased, or if the XCF limit on the number of members has been reached. Your application should cover cases in which no room is available within the group. Before running or installing your application, you should make the system programmer aware of your XCF group and member resource requirements.

Meaning: Environmental error. The system is being removed from the sysplex, and XCF permanently suspends all requests to join a group on this system.

Action: The action is dependent on your application. You might want to prepare your application for system termination. (See the topic on XCF in z/OS MVS Programming: Sysplex Services Guide)

Meaning: Environmental error. IXCJOIN with LASTING=YES is not allowed when the sysplex is in XCF-local mode. Permanent status recording requires a couple data set in which XCF can retain the member's status. XCF-local mode does not support a couple data set.

Action: This depends on your program. If XCF-local mode is not supported by your application, you must make the system programmer aware of this requirement. The system programmer will have to ensure that the system is not IPLed in XCF-local mode. Before running or installing your application, you should make the system programmer aware of your XCF group and member resource requirements. (See z/OS MVS Programming: Sysplex Services Guide.)

Action: Retry the request at least once. If the problem persists, record the return code and reason code, if applicable, and supply them to the appropriate IBM® support personnel.