Shutting off propagation of the Enqueue for PROFILE would only
apply to logging on to multiple systems in the sysplex. It would
not help if you wanted to log on the same image agani. The ISPF
LOG might be a bigger issue if you wanted multiple concurrent
logons to the same system.
Tom Marchant
On Mon, 29 Aug 2005 16:00:24 -0600, Paul Gilmartin <[EMAIL PROTECTED]>
wrote:
>In a recent note, Tom Marchant said:
>
>> Date: Mon, 29 Aug 2005 15:41:05 -0500
>>
>> It allows multiple started tasks with the same name. As others
>> have mentioned, there would need to be a way to handle numerous
>> data sets, including ISPF profile, log and list.
>>
>Most of these, according to DDLIST:
>
> *VIO NEW,DEL > ISPCTL0 SYS05241.T154937.RA000.SPPG.R0400516
< snip! >
> *VIO NEW,DEL > ISPWRK4 SYS05241.T154937.RA000.SPPG.R0400526
>
>... already have generated names with little collision hazard.
>(If you try again, one second later, it's likely to work.) The
>profile is the chief offender. And, as I noted, earlier, most
>of our programmers are satisfied to work with the exclusive ENQ
>propagation for ISPPROF suppressed; they accept last-update-wins.
>("Satisfied" insofar as they would find it less satisfactory to
>be required to log off one system before logging on to another.)
>
----------------------------------------------------------------------
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
