Your recollection is correct. Specifically, the profile is named ZDEFAULT.
On Fri, Jun 27, 2014 at 12:45 PM, Skip Robinson <[email protected]> wrote: > I hate to give a sloppy response, but 'at one time' an installation could > create a default ISPF profile called in whenever a user edited a data set > that did not already have a matching LLQ in the personal profile. This > default profile would be stored <somewhere> in the ISPTLIB concatenation > with <some name> and used initially. Default options like RECOVERY and > AUTOSAVE would be honored. That may all be handled by the ISPF setup > process now, but the point is that the installation can give the user an > initial profile, which the user can change if desired. > > Sorry for the fuzz. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > [email protected] > > > > From: "Vernooij, CP (SPLXM) - KLM" <[email protected]> > To: [email protected], > Date: 06/27/2014 06:52 AM > Subject: Re: PDSE member profile > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > Yes!. In our group, we all have activated an 'initial macro' that sets for > certain datasets some of the attributes we require, like STATS, AUTOSAVE > OFF PROMPT (to avoid PF3's unintentionally saving modifications). > > About what you call IBM chaos: if you look at the history of these > features, it is explainable how things grew this way. > First there was no (I)SPF, but there were member statistics as save by the > linkage editor etc. > Then came (I)SPF and they at some point in time found it useful to save > statistics, for ISPF use only. > Then they developed their own enq's (SPFEDIT) for editing several members > in a PDS while holding the PDS with DISP=SHR. > Then we got problems with batch updating PDS's that were in use constantly > by ISPF users, which was solved by batch updating the PDS with DISP=SHR, > which corrupted a PDS once in every 1000 to 1000000 times. > Then PDSMAN intercepted disp=shr batch by adding the SPFEDIT enq and the > linkage editor was doing likewise. > Now we have come to the chaos you describe and yes, someone with a > supervising view could have stopped this trend and decided to do this at > platform level, but this did not happen. > It is like a couple of guys developing a communication protocol for their > computer connections that suited their needs, but now it is used as > 'internet' and the total world economy depends on it, it should have been > developed differently. > > Kees. > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Paul Gilmartin > Sent: Friday, June 27, 2014 15:37 > To: [email protected] > Subject: Re: PDSE member profile > > 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? > > -- gil > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
