OS/2 Shareware BBS: 3 Comm/03-Comm.zip/lexon1a.zip/LEXON.DOC

Text File | 1995-09-13 | 19KB | 369 lines

** LEXON 1a **

_INTRODUCTION_

LEXON.RX allows users of Lexis/Nexis to access Lexis from a native
OS/2 comm app (communications application) known as "ZOC" (see
ABOUT ZOC below), enter their user ID, identify a matter or client,
select a library, conduct a search to any degree of complexity
desired, "mark" files for printing, and then at signoff, download
those files to a capture file named by the search date
(yymmddxx.cas, where x=sequential numbers) or any other name the
user desires.  I have found Lexon conducts searches easier and
faster than Lexis' own software, and since I know most of the "dot"
commands Lexis uses, it's much more user friendly.

Unfortunately, since this method uses character-mode access, you
will have to know the Lexis dot commands (.np for next page, .pp
for previous page, .nd for next document, .ns for new search, .so
for sign off, .pr for print document, .pa for print all documents,
.cf for change file, .m2 for modify level 2, etc.).  Once you
master those, however, you will probably be very happy with the
speed and ease of use Lexon provides.

If you call Lexis for an OS/2 version of their access software,
you'll probably be told that Lexis doesn't have such a critter and
that while you can access Lexis through any communications
application that provides VT100 support, you won't be able to
"print" documents to a file; you'll only be able to print to a
printer provided the application supports VT100P.  Well, things
aren't so bleak, at least when using ZOC, as LEXON.RX reflects.

Version 1a adds some minor improvements over the original version,
which was uploaded to OS2USER Lib 15, OS2BVEN Lib 1, the HAL-PC
BBS, and Pete Norloff's BBS.


_ABOUT ZOC_

LEXON.RX is a REXX program or script file intended to be run under
ZOC, Zap-O-Comm, an excellent shareware native OS/2 communications
program by Markus Schmidt that uses the PM (Presentation Manager -
GUI) interface of OS/2.  ZOC is generally available in a number of
places, including OS2USER and OS2BVEN forums of Compuserve, and is
usually in a file named ZOCxxx.ZIP, with the "xxx" replaced by a
version number.  At this time ZOC is up to version 2.10.  Lexon was
largely written under v2.05.  It may not work properly under
earlier versions, so users may need to upgrade to the newest
version.  If you use ZOC, please pay the shareware fee.  Markus has
written an excellent comm app, and we want him to continue
improving it.

This REXX program might run under other comm apps, provided they
support VT100 and support (that is, supply) the same REXX functions
and result codes ZOC does under the same names (e.g., ask, send,
timeout, zocresult(), zoccarrier(), wait, writeln).  Otherwise the
program would have to be modified to conform to the functions
provided.

!_PLUS_!:  One benefit of using ZOC is that it automatically
creates a file named CALLING.LOG, which appears in its primary
directory.  With Lexon, that log will show each call and which
client or matter the call was logged to (if you enter a client or
matter at the dialog box asking for one).  Then when Lexis bills
you, you can go back and confirm the charges.  And if you bill
clients for computer assisted legal research services by the amount
of time you spend, this will give you another way to do that
billing if your Lexis statement hasn't arrived yet.


_INSTALLATION_

1.   [Required]  Place LEXON.CMD, LEXON.ICO, and LEXON.DOC in your
     \ZOC directory.

2.   [Required]  Place LEXON.OPT in your \ZOC\OPTIONS subdirectory.

3.   [Required]  Place LEXON.RX into your \ZOC\SCRIPT subdirectory,
     unless you have a different path for scripts.

4.   [Required]  Place LOADREXX.CMD in the root directory of the
     drive from which OS/2 boots (for me that's G:\), unless you
     already have a way for REXXUTIL to be "registered"
     automatically in OS/2 (which means that its functions are
     loaded and available).  Then add the following line to the
     STARTUP.CMD file (if you don't have one, load E.EXE and enter
     this line, then save the file to the same root directory as
     STARTUP.CMD):

          CALL \LOADREXX.CMD

     You can also invoke LOADREXX.CMD from any OS/2 command prompt:
     just enter LOADREXX.

5.   [Optional, recommended]  Add the phone number and name of the
     network you use to access Lexis as follows:  Start ZOC, then
     "load" LEXON.OPT from the menu item "Options"; then if Lexon
     starts, terminate it:  First tell it not to log, then select
     the first cancel button available: but don't exit ZOC [you may
     have to hit ALT_- (hit ALT and "-" together); then open the
     Settings notebook by hitting ALT_S.  Then select the Auto-
     Reply page.  In the left column on that page, correct the
     initialization command to whatever ZOC uses for your modem
     (find it on the Modem page but don't include the ^M).
     Complete the right column to read:

          ^RUN=SCRIPT\LEXON.RX 1234567 NETWORK

     where 1234567 is replaced by the phone number of the network
     you use to access Lexis and NETWORK is replaced by the name of
     that network (e.g., MEADNET, COMPUNET, TYMNET).  Do the same
     for Button 1 on the Buttons page of the settings notebook.

     Don't worry if you don't do this, though:  If you don't
     include the number, you'll be prompted for it when you start
     Lexon.

6.   [Optional, recommended]  Create a program object for Lexon:
     Drag a program template from the template folder to the
     desktop, and when prompted for the program, enter
     [d:]\ZOC\LEXON.CMD, where d: is the drive where ZOC resides;
     and correct the path as appropriate.  Enter no parameters.
     For the working directory, enter [d:]\ZOC\.  On the settings
     page, place a check in the box to start minimized.  The
     LEXON.ICO should automatically be selected.  If it hasn't
     been, check the full screen box, then check the window box.
     If that fails, go to the General page and follow the procedure
     in the "find" box to select the icon.


_USING LEXON_

1.   [Starting Lexon]  To start Lexon, either click on the object
     you created in installation step 6 above, OR if you didn't
     create a program object, simply enter LEXON from a command
     prompt while in the \ZOC directory OR start ZOC, then access
     the Options menu, then Load LEXON.RX.  When ZOC starts from
     the program object or the LEXON.CMD file, it automatically
     loads the LEXON.OPT options file, and as soon as the
     initialization string is returned, it will start LEXON.RX.  If
     that string is not returned (i.e., if you don't see it on
     screen), Lexon won't start, but you can click on button 1 to
     start it.

2.   [Logging]  You will notice that the LEXON.OPT file creates a
     new log file for each day you log onto Lexis (named
     LXyymmdd.LOG).  A log file merely captures everything that you
     see on screen and provides a way to go back later and review
     something.  The log file is set on the Logging page of the
     settings notebook.  Log file names can be set to your personal
     preference.  If you want to use the same file ZOC creates by
     default, change this to read Z_^2_^1.LOG.  Over time, you will
     find the ZOC\LOG directory full of *.LOG files.  Unless
     there's something you want to save or refer back to, you can
     delete these.

3.   [No connection]  Lexon should recognize the conditions that
     indicate that a connection with the host service has not been
     made, but if you do not hear the typical modem "screech"
     indicating a connection within an appropriate time and you
     don't want to wait for Lexon to timeout (45 seconds), you can
     hit the ESC button.

4.   [Key remapping]  If you like to use the page up and page down
     keys, either remap those keys (under Options > Global > Key
     Map) or remap 2 other keys (such as F11 for previous page and
     F12 for next page) to provide these functions.  Enter .NP^M
     for page down and .PP^M for page up, and make sure the VT102
     box is checked and the ANSI is not (if you use the included
     LEXON.OPT instead of creating your own).  Just remember that
     you are remapping these keys for all uses, so expect them to
     behave the same in all applications for which you use VT102
     emulation.  This is a global remapping.  If you use a lot of
     VT102 communication and little ANSI emulation, then you could
     reverse those selections.

5.   [Nothing happening]  If nothing is happening when you think it
     should, you can terminate Lexon by hitting ALT_- (as described
     in Installation step 5 above).  Then you can either hang up
     (ALT_H) or try to proceed with Lexis as appropriate to
     wherever you are.

6.   [Changes in Lexis]  The Lexis/Nexis service periodically
     changes the messages that Lexon uses to invoke certain
     automatic operations.  If you note that a step that worked
     previously no longer works properly, please let me know.  If
     you logged that portion of your session, please email it to me
     so I can see Lexis' messages and make an appropriate change.

7.   [Confirm hangup]  ALWAYS make sure your modem line hung up
     after a session on line.  If it didn't, use ALT_H while in
     ZOC.  If you think the program is still waiting for something,
     terminate it by hitting ALT_-.

8.   Read the following Limitations carefully.


_LIMITATIONS_

Lexis may be accessed through a number of networks.  I've used
LEXON.RX to access Lexis through Meadnet, Compunet, Tymnet, and
Mead's 800 number.  It probably will not work with Sprintnet and
other networks through which Lexis can be accessed-- but only
because I haven't included the logon procedures.  If you know what
those procedures are (what Sprintnet, etc. send and how you're
supposed to respond), please let me know, and I'll see what can be
done to add them (if you're willing to be a "beta" tester).

!_VERY IMPORTANT_!:  Please note that you should not try to edit a
text string you've entered (a search or dot command, for example)
by using either the "Delete" or "End" keys.  Using communication
software like ZOC is not quite as directly "interactive" as Lexis'
Windows' software (although for me it's noticeably faster and a
little use has made it much easier).

To edit text you have just entered, you can delete by backspacing,
but trying to move the cursor to a particular position on the
display and hitting the "delete" key will not reveal what you have
done to the actual text string, and you will probably end up
sending something you do not want to send.  You may then have to
reenter your search or other command.  Even the backspace key
doesn't work as expected when you are modifying a previously sent
search string, so you will find it preferable to reenter the entire
string when modifying a previous search level.

More seriously, if you use the "End" key at all (and didn't remap
it as suggested in step 4 under Using Lexon above), you will clear
the display of whatever entry is there and will almost certainly
cause Lexis to abort when you hit "Enter".  That will put you back
at the access network's prompt:  Meadnet indicates this with "CLR
CONF" and an *; Compunet with "Host Name:"; and Tymnet tells you
"call cleared by request" followed by "please log in:".  Although
I have not tried Sprintnet or other networks, I suspect this
behavior is universal, the only variation being in the network's
next message.  If this happens, don't panic.  Lexon should hang up
(or you can do it manually).  Then log on again.

To protect yourself against that behavior, you can remap those
keys:  If you don't use VT102 emulation for anything, open the
Options menu, select Global then Key Map.  Click on the "E" or
"End" key and enter something, such as ^G (beep), .SO (for sign
off) or ^M (enter).  Do the same for the "D" or "Delete" key.  Then
hit OK and at the Options menu hit save.  Then in the Settings
notebook (under Options), change the emulation to VT102 (this does
not affect the program's telling Lexis it is using VT100 or VT100P
emulation).  This will have some effect on the way data is
received, but nothing serious that I've seen:  The only thing I've
noticed is that document delivery does not show the case or statute
name at the top of each page but merely "Transcript:Association".

If you encounter the network's clearing of your call and Lexon
doesn't recognize what happened by hanging up, please let me know
what network and what the display showed (exact words are critical:
if you logged the search, look in the log file).  If I can, I'll
try to fix it in a future version.


_"TECHNICAL" STUFF_

LEXON.RX is a fairly straightforward script/program, a bit simple
as access programs go, but it handles basic Lexis research under
ZOC (at least for me).  I'm still not particularly familiar with
REXX or the ZOC commands, so this is the best I've been able to
write so far, which is a another way of saying: don't be too
critical and don't complain if it doesn't do as much as you think
it should.

I suggest you look at LEXON.RX in the OS/2 editor (E.EXE) and read
the comments.  If you're not familiar with REXX, they're what's
between /* and */; other "*"s are window-dressing).  If you see
something described that appears different from how you operate in
Lexis, you will want to change it.  I'll be glad to offer
suggestions.  One thing you will want to change if you like the
idea of having the Library entered automatically: you can have
Lexon obtain that info before dialing Lexis by commenting the line
that skips the step provided under GETLIBRARY, so it reads /*signal
diallex*/.  Then change the prompt that references "TEX" so it
names your choices.  You can use the prompt as is and make any
entry you want, and your entry will be sent to Lexis, but it may
confuse you to see TEX mentioned.  If I knew what folks see in
other states, I might be able to do something about this via an
installation program.

If you encounter some situation that you think the program ought to
handle and it doesn't, let me know.  I may be able to fix it, but
remember that I'm just an OS/2 user, not a real programmer.  I
wrote this so I could access Lexis under OS/2, and the good folks
who operate Lexis haven't seen fit to provide a native software
package for OS/2, and I don't like the crashes and delays I used to
suffer in the Windows version.

In addition, while I'll be happy to help as time permits, please
don't expect real technical support.  This is not how I make a
living (I'd starve if it were).

Keep in mind that LEXON.RX only accounts for a few of the many
possible conditions that a search on Lexis can encounter.  You may
need to stop the program with ALT_- (hit ALT and "-" together) or
you may need to hang up (hit ALT_H).  Despite the tweaking I've
done, there are still glitches.  But that was true when I used the
DOS and Windows access software.  The plus here (at least for me),
is that I spend less time getting on and off (saves $, you know).


_NO WARRANTIES_

CAVEAT (legalese for "Listen up y'all"):  Lexon is freeware.  It
works fine on my system, but I have no idea how it will behave on
other systems or under conditions I haven't tried.  Therefore,
there are NO WARRANTIES, EXPRESS OR IMPLIED, WHETHER I KNOW ABOUT
YOUR USE OR SITUATION, which means you get what you pay for -- use
this program at your own risk -- I have no reason to believe
anything serious will happen, but I'm not responsible for anything
that goes wrong, whether with your phone bill, your hard disk, your
system, your relationship with Lexis, your marriage, your health,
your sanity, your business or practice, or anything else.

I received REXX help from the author of ZOC, Markus Schmidt, and
from Bill Schindler, Sysop in the OS2BVEN forum of Compuserve.
Bill and his wife Esther have authored a widely recommended book
named "Teach Yourself REXX in 21 Days".  If you are a REXXpert
studying my code, realize that some REXX commands and functions
don't seem to work in ZOC (in case you wonder why I did some of the
things I did when there might be better ways to do them from a
command prompt).


_FINALLY_
I'm making LEXON.RX and the other files available because it's a
shame to work so hard to get this far and not share it with someone
else, and because I'm the beneficiary of lots of freeware that is
a regular part of my system, and I feel I should repay part of the
debt whenever I can.  And, who knows, maybe this will be the
genesis of an OS/2 Lexis program (by a real guru, not me).

If you use this program and find it helpful, please let me know.
If I know there are folks using it, then when I make improvements,
I know to upload them.  If I think I'm the only one in the world
using this stuff, you may not see another version.


David Eckman
75430,[e-mail]
September 13, 1995


Files included in the zip file:

File Name      Date      Description and File Location
---------      --------  ----------------------------------------
FILE_ID.DIZ    08-31-95  A description of Lexon.
LEXON.DOC      09-13-95  This file.  Place this file in the ZOC
                         directory (or anywhere it can be found in
                         the future).
LEXON.CMD      09-13-95  A short batch file to start Lexon.  Place
                         this file in the ZOC directory.
LEXON.RX       09-13-95  REXX program or script for use in ZOC to
                         access Lexis; place it in the ZOC\SCRIPT
                         directory.
LOADREXX.CMD   08-31-95  REXX file to load REXXUTIL functions;
                         place this in the OS/2 root directory and
                         call this from STARTUP.CMD.
LEXON.OPT      09-13-95  Options file for use during Lexis access;
                         place it in the ZOC\OPTIONS directory.
LEXON.ICO      08-31-95  An icon for use with the Lexon program
                         object if one is set up as described
                         above.  Put this file in the ZOC
                         directory (or anywhere it can be found in
                         the future).