NATURAL PROCESS Extends NATURAL to Operations Center

continued from page 7
Each ADAMINT source module
may not exceed 380 lines.
Generation of ADABAS SQL syn-
tax requires full ADABAS field
names. Currently, a 50-line limit
per ADABAS SQL syntax state-
ment exists. Therefore, it may be
necessary to limit the size of
field names in PREDICT to a
minimum so this restriction is
not exceeded. You can, however,
create userviews for conversions
that exceed this ADABAS SQL
restriction.
FLDMODE = DYNAMIC is not
supported; however, syntax will
be generated for full record ac-
cess and update for the
ADAMINT entry point
converted. It will be necessary
for modification of user programs
if FLDMODE is used for u~date
entry points.
READR= entry point names may
not be duplicated. In other words,
two FINDSETs may not reference
the same READR entry point
name. This will cause duplicate
entry points to be created in the
I generated COBOL program.
File COUPLING will not be sup-
ported. AMIZSQL assumes one
file per userview module.
Literals, spacing, and MUIPE
interleaving (PEGROUP and
ENDPG notation) will not be
supported. You may modify the
generated program to pass infor-
mation as required in the link-
age section.
The special character "(" or ")"
should not be used in comments
within an ADAMINT entry
point.
* COBOL reserved words are pro-
hibited in PREDICT field
definitions.
The ADAMINT ONEP MOD-
ULES statement must reflect the
member names of the USER-
VIEW modules within the PDS.
For CICS, the application DWA
must be large enough to store the
generated COBOL DWA. The
DWA must be saved and restored
correctly by the user application
between returns to CICS
14 (pseudo-conversational) .
CHFILE macro is not supported.
This functionality is not pro-
vided in ADABAS SQL.
All macro parameters dealing
with cluster users are not
supported.
By creating the COBOLIADABAS
SQL program as a subprogram, the
calling user program is not "gar-
baged-up" by duplicated record
buffer areas, duplicated data
names, etc., which would require
manual intervention to correct.
Also, all programming languages
that call ADAMINT may have their
ADAMINT programs converted to
ADABAS SQL.
AMI2SQL serves as an instruc-
tional tool for understanding the
relationship between ADAMINT
and ADABAS SQL. AMIZSQL doc-
uments the ADAMINT source
statements within the generated
COBOL source for this purpose.
By converting all of the ADAMINTs
at one time, it is possible to keep
ADABAS SQL cursor names
(ADABAS CIDs) unique. This is I
APPLICATION CALLING ADAMINT
SUBROUTINE
USER APPLICATION
call 'lokexl' using search-criteria.rspcd.
entry lokexl
call 'adabas' ,(~arameter list)
mvc results to user program ...
ADABAS I
important for problem determina-
tion and command log analysis.
AMI2SQL will convert both batch
and CICS ADAMINTs. The appro-
priate SAVE and RESTORE
ADABAS SQL commands are gen-
erated for pseudo-conversational
CICS programs.
AMIZSQL requires ADABAS SQL
Version 1.2 or higher, and PREDICT
Version 2.1 or higher.
In Summary
For those of you who are tired of
the ADAMINT maintenance night-
mare, or for those who are consid-
ering converting ADAMINT
applications to ADABAS SQL, or
those who wish to enhance existing
ADAMINT applications by using
the new features of ADABAS 5,
AMIZSQL is the tool for you.
Price and availability of AMIZSQL
are to be determined. Your Account
Representative will contact you
when more information is available.
APPLICATION CALLING
COBOL SUBROUTINE
WITH ADABAS SQL
USER APPLICATION
call 'lokexl' using search-criteria.rspcd.
COBOL/PLI
ADABAS SQL MODULE
...
entry 'lokexl' using search-criteria.rspcd.
execadabas
open xxxx
end-exec
move data to user program ...
ADABAS