Re: Webfacing and Display Device Name

Yeah, that's a possible option. But it will require some serious tinkering
to bypass this. Still...might be easier to do that than have to worry about
this at all.

Thanks.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Bob P. Roche
Sent: Friday, September 21, 2007 2:27 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Webfacing and Display Device Name

If you need this why not adjust the program not to look at this part of
the code? By specifying the default you are bypassing this security
portion of the program and allowing anyone who can get the web access to
use it anyway. Another option is to determine where it is running from and
bypass this code only for the programs running webfaced not the green
screen version. I'm not familiar with coding this, but I know there is a
way to determine which way it is being run. Someone will know how to do
this, If not Monday I can ask another programmer who has done this type of
specific to webfaced coding.





"Shannon ODonnell" <sodonnell@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
09/21/2007 02:11 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] Webfacing and Display Device Name






Hello List,



Does anyone know.is there a way to specify a default device name for a
webfacing application? I have a user-written app that looks for specific
device names (i.e., they must have been previously defined within that
application) and if it does not find that device the job signed on with,
it
logs the user off. I'm thinking if I can specify a display device name on
the web facing session, that I could get around this problem. I guess I
could add all the possible QQFxx jobs the web facing server generates but
I
was hoping to be able to avoid that if possible.



TIA