and following is the NFTP card:
-----------------------------------
FUNCTION=ADD
SFILEID=sorce dataset
SACCOPT=SHARED
SFILEORG=PO
XMODE=TO
RMTNODE=AAIB
RFILEID='target datset
RFILEORG=PO
RSTATOPT=MAYEXIST
RSECURP=('xxxx','****')
SSECURP=('xxxx','****')
COMPMODE=A
WAIT=YES
PRIORITY=2
WAITTIME=10
/EOR
FUNCTION=QRYALL
------------------------------------------
and the NFTP returned Reason code 392, which means:
RSN = 392 means ATTRIBUTES OF PDS NOT SUPPORTED BY BPAM. THE PDS BEING TRANSFERRED HAS ATTRIBUTES THAT ARE NOT SUPPORTED BY BPAM. POSSIBLE REASONS ARE: 1.ITS RECORD FORMAT IS VARIABLE SPANNED (VS) OR VARIABLE BLOCKED SPANNED (VBS).
2.THE ATTRIBUTES OF THE SENDING AND RECEIVING DATA SETS ARE INCOMPATIBLE.
3.THERE IS MORE THAN ONE NOTE LIST TTR FOR ONE MEMBER.
4.TWO MEMBERS HAVE THE SAME TTR BUT BOTH ARE REAL MEMBERS.
========================================
Attached the NFTP log for reference:
********
PROCESSING STARTED FOR REQUEST NUMBER = 936 ; REQUEST NAME = RCMNFTPK
CONVERSATION ALLOCATED WITH QAFTPB01 AT 19:13:40
FILE TRANSFER STARTED ON LOCAL REQUEST HANDLER FOR REQUEST NUMBER 936 ON 09/09/28 AT 19:13:40
SAF/RACF SECURITY VERIFIED BY USER-EXIT ROUTINE
MESSAGE FROM USER-EXIT ROUTINE ZLNVPREX; MESSAGE = Password not verified for userid C207580
- Originating userid matches sending userid on originating system send request (No MAJO)
END OF PROCESSING OPTION CHANGED FROM NOT-SPECIFIED TO KEEP
DATA SET IS ALLOCATED WITH FILE STATUS OPTION MUSTEXIST , FILE ACCESS OPTION SHARED AND END-OF-PROCESSING
OPTION OK KEEP , NOT OK KEEP
IGD103I SMS ALLOCATED TO DDNAME DVGFI01
MEMBER CHN$DLM AND MEMBER EDQCT0M HAVE THE SAME TTR BUT BOTH ARE REAL MEMBERS
MEMBER CHNCY2M AND MEMBER EDQCU0M HAVE THE SAME TTR BUT BOTH ARE REAL MEMBERS
MEMBER CHNJRBM AND MEMBER EDQC1CM HAVE THE SAME TTR BUT BOTH ARE REAL MEMBERS
MEMBER CHNJRCM AND MEMBER EDQC9CM HAVE THE SAME TTR BUT BOTH ARE REAL MEMBERS
...
so seems different PDS members got same TTR, but how could I resolve this problem??
