On Tue, 8 Oct 2013 10:03:25 -0400, Kurt Quackenbush wrote: >> Also, it used to be the case that only one instance of the SMP/E dialog >> was allowed within a single TSO/ISPF session - a 2nd concurrent >> invocation in split screen was not allowed and would produce a failure >> message.. > I had suffered that, and attributed the problem mostly to DDNAME conflicts. Do both splits try to allocate SMPCSI?
>Not so any more. Check out APAR IO18093 (and its subsequent fixes). > Much appreciated. Concurrent updated are still prohibited; a reasonable restriction. Does this also prohibit concurrent updates, one from ISPF and one from batch? I notice subsequent APARS for ISPF variable pool contention. I suppose it improves by successive approximation. Breathlessly awaiting a Rexx API. (Turning blue.) Thanks again, gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
