| DESCRIPTION OF ENHANCEMENTS |
VA FileMan SQLI Interface (SQLI)
data. After installing this patch, note that the DMSQ MENU will not be
<tab>;;21.0;VA FileMan;**38**;July 28, 1997
CHECK^XTSUMBLD results:
Routine Name Before Patch After Patch Patch List
============ ============ =========== ==========
DMSQ new routine 10102863 38
DMSQD new routine 8773388 38
DMSQE new routine 843826 38
DMSQF new routine 9792265 38
attached to any other existing menu; it is stand-alone, to be assigned as
DMSQF1 new routine 8310046 38
DMSQF2 new routine 8370804 38
DMSQP new routine 2371815 38
DMSQP1 new routine 3565656 38
DMSQP2 new routine 6721470 38
DMSQP3 new routine 11874271 38
DMSQP4 new routine 2151271 38
DMSQP5 new routine 5423594 38
DMSQP6 new routine 10074783 38
DMSQS new routine 3197279 38
needed.
DMSQT new routine 11672859 38
DMSQT1 new routine 1181888 38
DMSQU new routine 10589283 38
Installation Instructions:
==========================
Before starting: Place and protect ^DMSQ
This patch brings in a new global, ^DMSQ. As usual with new globals,
place it before running the install (the default location of the install
will otherwise be used). You can translate it for ease of access.
Journaling is unnecessary.
For global protection, a standard approach can be used, such as the
following:
DSM for OpenVMS - System (RWD), World (RW), Group (RW), and User (RW)
OpenM - Owner (RWD), Network (RWD), Group (N), World (N)
MSM-DOS - System (RWD), World (RWD), Group (RWD), User (RWD)
The installation of this patch is mandatory because the software includes
NOTE: Users may remain on the system during this installation. There's no
need to disable logons either.
1. There's no need to disable mapping (these routines won't need to be
mapped).
2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu. This
option will load the KIDS package onto your system.
supported references (entry points and DD structures) that may be called
3. The patch has now been loaded into a Transport global on your system.
You now need to use KIDS to install the Transport global.
4. On the KIDS menu, under the 'Installation' menu, use the following
options:
Print Transport Global
Compare Transport Global to Current System
Verify Checksums in Transport Global
Backup a Transport Global
by application code. So, even if you don't plan to implement
(5. Users don't need to logoff. They may remain on the system while this
patch is installed.)
(6. There isn't any need to place TaskMan in a WAIT state.)
7. On the KIDS menu, under the 'Installation' menu, use the following
option:
Install Package(s):
INSTALL NAME: DI*21.0*38
SQLI as a basis for a vendor SQL product, you still should install this
==========
Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu
Options, and Protocols?'
8. MSM Sites - Answer YES to the question 'Want to MOVE routines to other
CPUs?'. Enter the names of your Compute and Print server(s).
9. MSM Sites - After the installation begins, you will be prompted to
enter a DEVICE. After the device has been entered, KIDS will pause.
patch.
At this time, you need to go to each of the CPUs that were identified
in the previous step and start a job that will allow them to receive
the routines included in the patch. On each CPU, do the following:
a) >D ^XUP - to set up the programming environment
======
b) >D ^XPDCPU - to start the job that receives the routines
=========
c) Select INSTALL NAME: DI*21.0*38
==========
This completes the installation instructions.
The installation instructions for loading this patch are entirely
contained below. You don't need to get the SQLI documentation for this
purpose. (The SQLI documentation doesn't include installation
instructions for loading this patch.)
Documentation for Implementing SQLI
===================================
Implementing SQLI is optional. See the VA FileMan SQLI Site Manual for
more information about populating the SQLI files and, furthermore,
This patch installs the foundation for building an interface between VA
incorporating vendor SQL products and building an SQL system. This manual
is to be reproduced and distributed by the National Center for
Documetation (NCD). This manual will also be available in Acrobat PDF
format from the SQLI home page:
http://www.vista.domain.ext/softserv/infrastr.uct/sqli
The SQLI home page will be a source of current information, including case
studies of how sites have chosen to implement SQL access to their systems.
FileMan's data dictionaries and a vendor's M-based SQL data dictionaries.
Test Sites
==========
Two test sites have loaded this SQLI patch and have implemented a full SQL
system (with the additional vendor software that's needed). These are the
VA medical facilities at San Francisco (VISN 21) and Brooklyn (VISN 3).
Four additional test sites are in the process of establishing a system
that is based on SQLI: VA medical facilities at Seattle (VISN 20),
Phoenix (VISN 18), West Haven (VISN 3), and Palo Alto (VISN 21).
This patch will bring in a new global, ^DMSQ, and several new routines and
Supported References
====================
DATA DICTIONARIES
All the files, fields, and cross-references included in this patch can be
referenced directly without integration agreements. This enables vendors
to create mapping utilities using the SQLI structures. Specifically,
these are the files in the 1.52 to 1.53 number range, all stored in ^DMSQ.
options in the DMSQ namespace.
See the SQLI Vendor Manual on the SQLI home page for more specific
information.
CALLABLE ENTRY POINTS
The following routine entry points may be called in application code.
They are primarily designed for use in vendor mapping code. See the SQLI
Site Manual and SQLI Vendor manual for more information.
Populating SQLI files (Projecting the Interface)
ALLF^DMSQF - non-interactive call
SETUP^DMSQ - interactive call (used in the DMSQ PROJECT option)
Populating the SQLI_KEY_WORD file (with the SQL vendor's keywords)
KW^DMSQD - loads keywords from a specified global
Populate the SQLI_TABLE and SQLI_PRIMARY_KEY row counts (to accumulate
statistics that vendors may want to use to optimize queries)
ALLS^DMSQS - all tables
STATS^DMSQS - one table
The new files (in ^DMSQ) are in the 1.52 to 1.53 number range. Each one
Naming algorithms to generate SQL-compatible names
$$SQLI^DMSQU - general check
$$SQLK^DMSQU - general check including keyword check
$$FNB^DMSQU - specific check for table names
$$CN^DMSQU - specific check for column names
DIRECT MODE UTILITIES (also available via the DMSQ MENU option)
These calls are for direct mode use only (issued interactively at the
programmer prompt). They are not supported for use in application code.
See the SQLI Site Manual for more information.
begins with SQLI, e.g. the SQLI_TABLE file. None of the files includes
MAIN^DMSQE - lists files/fields that couldn't be projected
RUNONE^DMSQ - re-run projection for one file (for testing only)
Routine Summary:
================
The following routines are included in this patch. The second line of
these routines will look like:
|
