> want to support what your customers do You got it!
> issue an OPEN TYPE=J Unfortunately I'm not doing the OPEN, FTP is. The problem is not with the DISP per se. The underlying problem is that FTP has the world's worst RECFM and LRECL defaults, something like RECFM=U, LRECL=1024 (LRECL from recollection). I have several strategies for dealing with the problem and the strategy I choose depends on among other things whether we are in a PDS member DISP=NEW/MOD situation. The bug was in choosing the wrong strategy due to the logic error I described. My strategies are good -- I was just choosing the wrong one. Did somebody say use LOCSITE? Unfortunately LOCSITE is not effective with //DD: As the FTP is z/OS to z/OS a clever FTP client would pick up the dataset attributes from the server but z/OS FTP is not that clever. I am contemplating instead the use of IEFQMREQ to modify the JFCB to add LRECL and RECFM but I have not yet committed to that route. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Gerhard Adam Sent: Saturday, March 05, 2011 2:32 PM To: [email protected] Subject: Re: Difference between DISP=NEW and MOD for a PDS member? I'm not sure I'm interpreting this properly, but it sounds like you have a product and want to support what your customers do when accessing a PDS (even if they code it badly). My confusion comes from your reference to the JFCB, since it suggests that you are checking to see what they have coded, ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
