Re: Re: Fullscreen application Specs

Hi Roc,

Well not an editor bug, but then it's a gcic / system bug ;) ... err
or "anomoly" :

In CMS while, it doesn't make much sense,  I can do a LINK * 191 291
rr read, then ACC 191 g, and there's no problem .... other than I
don't have a writeable A disk anymore ;)

I guess  in your gciic environment, it's a "pseudo  CMS /CP" environment ?

Is there something special about dev 191 in that context ?  (would seem to be)

Or to put it another way, what is generally different in GCIC,
compared to CMS for the 191 device?

... Or is 191 even "special" to CMS? ...    (Is it more the "A" disk
designator which is "special" ?

Mike


But if we're *dialed* in ... then there is no 191 disk right ? ...
As the user is not LOGGED in.

I didn't try to acc the CMSUSER 191 disk,  ... which *should be
accessible  (read only).    I tried to acc

On 8/4/10, Rocky <[email protected]> wrote:
>  Mike just wrote me off line :-)
>
> ===================================== ===========================
> Hi Roc,
>
> Found a bug / problem
>
> I did a CMS LINK BREXX 191 291 rr read
>
> Then I meant to type CMS ACC 291 g ... but accidentally typed CMS ACC 191 g
>
> Seems to have hung the interface
>
> I just reconnected, and i put me back at the output screen from the link
> command ...  shows dec=000000 at the bottom of the screen but it seems to be
> stuck there
>
> [5:41:06 PM] Mike Stramba: just connected another session, got as far as the
> flist screen, stuck there.
>
> Also it let me logon as BREXX again
>
>
>
> =============================================================Too bad
> Mike
>
> it happened at 6:00 in the evening your time.
> I had just gone to bed - Remember that I am way ahead of you on the clock
>
> And there was no one around to reboot the machine.
>
> I think Dave warned me that this could happen.
>
> It's not a bug as far as the editor is concerned since in your own
> environmnet this is not an issue.
>
> OK -
> I will have to prevent you from doing an access to the 191 disk but that is
> not part of the editor application.
>
> Actually I can handle that pretty easily.
>
> BUT for the record you were not stuck and the application was working
>
> By the time that you were working all the programs were in Memory but
> the task you were working the one that did the CMS ACCess
> was stuck on trying to access the "A" disk for the reply
>
> YOU logged onto another session suscessfully - after all its a multi tasking
> environemet
>
> Got as far as the FLIST screen - Probably got stuck on the A DISK there also
> Ater all it does a LISTF and reads the output from the a disk
>
> Its up again.
>
> I don't consider that an editor bug - so I am still bug free for two days
>
> Roc
>
>
>
>
>
>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>