Kees is correct. FTP doesn't support ISPF profiles. It was specifically modified to handle user data area for the member in the PDS directory.
ISPF editor is just an editor. Why the OUCH when every other editor (including UNIX) allows you to change the edit settings? If you want a dev environment, then you install a dev environment (e.g. SCLM, Changeman, Endeavour, CVS, ...). As for edit recovery, it is associated with the user and that is the correct choice. In z/OS dev environments, we have member locking which would make shared recovery viable. Outside that environment, member lock has been lost once the edit terminates for the member. Allowing recovery in this situation can lead to confusion or failures. Would you trust automatic recovery of a SYS1.PARMLIB member? Jon Perryman.. On Friday, June 27, 2014 6:37 AM, Paul Gilmartin <0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > >On 2014-06-27, at 07:21, Vernooij, CP (SPLXM) - KLM wrote: > >> I doubt it, the profiles are an internal ISPF thing and their definitions >> saved in the user's personal profile dataset. Which/whose settings should >> FTP use? >> >Are you saying that if multiple users have write access to a PDS >for purposes of team development (ISPF supports this operation >(I used to believe well)), they may follow inconsistent conventions >with respect to NUMBER, STATS, RECOVERY, ...? > >Ouch! > >In case of team development, such a profile should belong to the >library, not to the individual developer(s). > >Hmmm... Suppose one developer's edit session crashes, but RECOVERY >is on. Can editing that member be resumed and recovered by another >team member? > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
