A fix is available
APAR status
Closed as program error.
Error description
MSC session initiation (/RST LINK) fails with error messages DFS3213 and DFS3672 because IMS cannot find an MSC NODE name that matches the PLU name passed by VTAM when the SCIP exit is driven. The PLU name passed is the USERVAR rather than the real name. VTAM APAR OA20677 changed the way VTAM handles USERVARs. If a USERVAR is defined in VTAM it will be passed when the SCIP exit is driven. Before the APAR the real PLU name (APPLID) was passed. The messages issued when the SCIP exit is driven: DFS3213I 9:29:12 REMOTE INITIATED LINK START FAILED, REASON CODE=04. PARTNER ID DW. INITIATOR IS NODE I66X. DFS3672I 9:29:12 SESSION ERROR. TYPE=SCP CODE=34 QUAL.=04 MSG=3213. In this case, I66X is the USERVAR and cannot be found in a search of MSC NODE names which are usually APPLIDs so the link start attempt is rejected.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All IMS V10 systems using multiple systems * * coupling (MSC), or intersystem * * communications (ISC) and VTAM USERVAR. * **************************************************************** * PROBLEM DESCRIPTION: /RESTART LINK fails with message * * DFS3222I SIMLOGON RC=10 FDB2=10 SENSE * * = 08390003, and partner receives * * DFS3213I RC = 04. /OPEN static ISC node * * fails with message DFS2051 RESYNCH * * FAILED and DFS2085I SESSION TERMINATED * * RC = 260. * * * * Forward Fit PK77759 V9 * **************************************************************** * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** After applying VTAM APAR OA20677 which changes the way VTAM handles USERVARS for LU6.1 sessions, MSC VTAM links and ISC static nodes fail when they are started. ISC ETO nodes may fail too if they don't recognize the PLU symbolic USERVAR name. This VTAM APAR changed the PLUNAME in the bind image pointed to by word 4 in the SCIP exit input parameter list to the USERVAR name instead of the primary's APPLID name. The IMS SCIP exit bind processing searched for the LUNAME using the primary's APPLID name. This causes the PLUNAME to not be recognized and the bind is rejected. IMS XRF was not being used but the USERVAR names were set using the VTAM command F IMSVTAM,USERVAR. Additional keywords: MSGDFS3213I MSGDFS3222I MSGDFS2051 MSGDFS2085I MSGDFS2063I
Problem conclusion
AIDS: RIDS/DCS RIDS/CNTRL DCS CNTRL GEN: KEYWORDS: *** END IMS KEYWORDS *** The IMS SCIP exit in module DFSCNXA0 was changed to search for a matching control block (LLB for MSC link and VTCB for ISC node) using the symbolic USERVAR name first, then the PLU APPLID name second, and if either is found, the bind is accepted. Publication Changes: Messages and Codes Vol 1 manual ( GC18-9712-01 ) will be changed for message DFS3213I reason code 04 to add: 04 - The Partner ID specified does not exist on this system or the logical link for NODENAME = nodename could not be found.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PK78241
Reported component name
IMS V10
Reported component ID
5635A0100
Reported release
010
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2009-01-07
Closed date
2009-02-05
Last modified date
2009-10-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK43819
Modules/Macros
DFSCNXA0
| GC18971201 |
Fix information
Fixed component name
IMS V10
Fixed component ID
5635A0100
Applicable component levels
R010 PSY UK43819
UP09/02/13 P F902
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.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVRBJ","label":"System Services"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 October 2009