Howdy,

We use a menu system which upon application failure exits the session.  However,
I've never been adverse to changing things as new tools become available.  In
South Texanese that means "ya just throw the sucker in there an' I'll figger a
way to use ett".

jt

----------
From:  Lee Gunter[SMTP:[log in to unmask]]
Sent:  Tuesday, May 05, 1998 11:46 AM
To:  [log in to unmask]
Subject:  Re: SHOWVAR enhancement

Scott makes an assumption when he says "most customers ..." -- this means
we're outside the norm because we use a menuing system.  If a user program
aborts in this case, the session is still intact unless the user exits from
the menu which then triggers a logoff.  The :SHOWVAR enhancements Jeff
proposes would be a big help to us because most users do not have access to
a CI prompt from their menus, thus we cannot walk them through :SHOWVAR,
:LISTEQ (this is another enhancement I'd love to see -- i.e., the ability
to view another user's file equations), or similar commands.

Do most other sites' applications fit Scott's model, or are we truly in a
minority?

Thanks,

Lee Gunter
Regence Blue Cross Blue Shield of Oregon / Regence HMO Oregon

mailto:[log in to unmask]
voice...503-375-4498     fax.....503-375-4401
==========================================================
The opinions expressed, here, are mine and mine alone, and do not
necessarily reflect those of my employer.





From: [log in to unmask] on 05/05/98 02:45 AM

Please respond to [log in to unmask]


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: SHOWVAR enhancement




> Date:          Sat, 2 May 1998 14:49:33 -0400
> John Korb wrote:
> >
> > At 02:01 PM 1998/05/01 -0700, Jeff Vance wrote:
> > >Hi all,
> > >
Scott McClellan added:

IMO, I don't think the :SHOWVAR @;JOB= "enhancement" will help debug
this type of error.
Why? Most customers use a logon UDC like the following:
logon
option logon
setvar ...
setvar ...
setvar ...
file ...
file ...
..
run a.b.c ...
bye
So the user logs on and then the application aborts. They call the
"system administrator" type with the problem stagement "My program
aborted with DBOPEN error...why?"
So what are you going to do? You can't do a :SHOWVAR @;JOB= on a
job/session that does not exist anymore because it logged off after
the DBOPEN error killed the program. Bottom line if you want to debug
the program you are going to have to put some appropriate
debugging/logging logic in the program so that it save enough info
that you can debug it. Or you are going to have to duplicate the
problem.
I just don't see how the :SHOWVAR enhancement is, in general, going
to make it easy to solve this problem.
BTW: this does not mean that I am against the :SHOWVAR enhancement, I
just think that the main value is to be able to display USER
vairables that have been set by other, currently executing, jobs and
sessions.