Re: POP and WSG

David

At 12:49 PM 5/1/1998 -0700, you wrote:

-snip-

>We're also interested in using the Work Station Gateway. We think it might
>be very useful for allowing our customers access to our database. Is anyone
>else using this? How is it working out for you? Any "gotchas" to be aware
>of? Is security a problem?

I've activated WSG on our development machine. It offers a very basic way
to Internet-enable your native apps. As far as it goes, it's pretty cool.
It is essentially a 5250->HTML converter (screen scraper). INET, who write
another WWW server for the 400, have a similar product called Webulator.
Try <http://www.inetmi.com> .

Considerations are well-discussed in the TCP/IP Config & Ref, but here're
are my Sunday a.m. recollections:

1. Function keys are not live, you need to click on buttons.

2. Screens are not refreshed when the 400 sends additional data (like
status messages). This is because of the nature of HTML, which does not
poll or send refresh requests without user intervention. A number of other
products, like BusinessLink's stuff and IBM's HostOnDemand, are based more
or less on Java. These are Internet-capable apps that work like CA, etc.,
but as native TCP/IP apps.

3. A benefit is that you can add HTML specs to your DDS. These will be
ignored for native 5250 screens, but will be added to the HTML stream that
results from the conversion. Allows almost anything you can do with HTML,
including, I suppose, ActiveX and JavaScript. I must say, there aren't many
examples yet published on how to _really_ take advantage of this stuff.

4. Logging is possible. Check the manual for details. At least in v4r1,
there's an exit point for 'WSG Server Sign-On Validation'. Run the
WRKREGINF command and look there. Again, rtfm (standard 'unix' jargon for
'read the fabulous manual').

5. Devices are randomly assigned as in CA95/NT are—QPADEVnnnn. You need to
be sure not to modify the top part of your signon screens, so that logging
can retrieve the device name (rtfm for more). But you _can_ get the IP
address by any of the various means heretofore (ooh!) suggested. Also,
format DEVD0006 of the Retrieve Device Description (QDCRDEVD?) API has the
IP address for whatever device has been assigned.

The best source is the manual. You should also look at the DDS manual,
under the HTML keyword. There was also some stuff at IBM's web site, but it
was mostly suggestive of possibilites. Some of it is extracts from the
manual. (I couldn't find it this a.m.—maybe it is no more?)

Let me throw another idea in here—Net.Data. This gives direct access to 400
data via SQL, REXX, and system calls. And it's a part of the OS. And way
cool, IMO.

HTH

Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN  55401-2499
(612) 371-1111 x480


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---