RE: Re: Fullscreen application Specs

Its more complicated than that Mike
 
I need to allow you to signon on to two sessions
or at least make the connection ---
We still have to do copy and paste from one session to another
 
The actual naming conventions is not an issue the user ID is enough if I
check that two users can't log on with the same id,
This is going to take some thought on how to do it right and how the
application is going to be used
 
Keep shooting off your suggestions -- Eventually we will get a consensus -
right now it all ideas
The numbering conventions might be good but dificult for you to find your
autosave if 15 people are autosaving
which is yours which gets erased
 
more complicated ---
Wrie your suggestion in pseudo code and see how it works
 
Roc
 


  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of
Mike Stramba
Sent: Thursday, August 05, 2010 20:54 
To: [email protected]
Subject: Re: [H390-VM] Re: Fullscreen application Specs


  

>But we are all using the same autosave name

>I need to fix that and a few other places so that it will autosave with a
uniqe name.
>Best is th signon name - but then I have to ad the checking to allow you to
sign the same user only inone session concurrently.

How about sign-on-name + session ctr ?

Brexx autoXXXX Brexx auto0001
Brexx autoXXX Brexx auto0002
...
Then don't have to limit the logon name to only one logon

On 8/5/10, Rocky <[email protected] <mailto:rocsystems%40gmail.com> >
wrote:
> Mike
>
> Actually there is no problem with File contention
> What happened to you was Program Check -Because some DUMB programmer
didn;t
> check his code thouroughly -
> Same thing happened to Paulo - Fixed now
>
> File contention is enqueued.
>
> YOu read a file - for the second or so that you are reading it is enqueued
> but as soon as you finish I can read it.
>
> We both work in memory - YOu say save and I say save --- The save routine
is
> in enqueued whoever get there last wins
>
> Where I do have a problem is on the utity files
>
> autosave
> and the flist
> and some others
>
> Most of them are also enqueued so there wont be an abend problem
> But we are all using the same autosave name
>
> I need to fix that and a few other places so that it will autosave with a
> uniqe name.
> Best is th signon name - but then I have to ad the checking to allow you
to
> sign the same user only inone session concurrently.
> I built the fields for that is the design - just didn;t get around to
> implementing.
>
> Not a big issue and once we dide how to use this magical tool We will be
> smarter
>
> I saw that you linked to the BREXX DISK as "G"
>
> GREAT --- Now I can see all the "C" stuff in full screen mode and maybe
> understand something
>
> ROC
>
>
>
>
> _____
>
> From: [email protected] <mailto:H390-VM%40yahoogroups.com>
[mailto:[email protected] <mailto:H390-VM%40yahoogroups.com> ] On
Behalf Of
> Mike Stramba
> Sent: Thursday, August 05, 2010 18:44
> To: [email protected] <mailto:H390-VM%40yahoogroups.com> 
> Subject: Re: [H390-VM] Re: Fullscreen application Specs
>
>
>
>
> Roc,
>
> As we've just seen there's a problem with file contention / multi
> users accessing the same file.
>
> If possible I would like to see BROWSE of a file possible if it's
> already opened for EDIT by another user.
>
> I guess EDIT of a file by two users could be permitted but only if
> the "second" user to edit the file is forced to save the file under a
> different name than the original. That could get messy though, if
> the first user decides to try a "save as" using the same file name as
> User#2 used.
>
> Probably needlessly complex, unless you're really bored / looking for
> a challenge ;)
>
> Speaking of "Save As", is there a way to do that yet?
>
> On 8/5/10, paoloG <[email protected] <mailto:crc%40alce1.tuttopmi.it>
<mailto:crc%40alce1.tuttopmi.it> >
> wrote:
>>
>>
>> --- In [email protected] <mailto:H390-VM%40yahoogroups.com>
<mailto:H390-VM%40yahoogroups.com> ,
> "Rocky" <rocsystems@...> wrote:
>>>
>>> Hi all
>>>
>>> HERE IS THE GOOD NEWS
>>> There is no BAD NEWS.
>>>
>>> The SAVE- FILE routines are now working - You can actually edit and then
>>> save the file
>>
>> Rocky,
>>
>> I created a little file (ROCKY TEST A), the deleted all the lines -
>> typed I on line 000000 to create a new line and got a terminal stuck.
>> From other terminals DIAL CMSUSER didn't work.
>>
>> I permitted myself to restart CMUSER Virtual machine and now everything
is
>> working fine.
>>
>> Regards.
>>
>> Paul
>>
>>
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>>
>
>
>
>
>