|
What we do with the ADS/O or ADS/A
Dialogue …
Create a structured COBOL program for
each dialogue using automated tools.
All comments in the original code can
be carried through to the migrated code.
Each copy IDMS is converted to a COBOL
copy statement with IDMS copybooks becoming COBOL copybooks.
Subroutines are converted to COBOL
sections and all call statements become COBOL Perform
thru exit.
Copybooks are inserted for the SQLCA
and additional working storage areas including record
areas, work areas, screen buffer areas, and necessary
SQL and CICS areas.
What about the map definition and I/O …
For each ADS/O or ADS/A map or menu,
the macro’s necessary to generate a BMS map set definition
and a COBOL copybook that reflects the structure of the
BMS map buffer are generated.
Replace all map related statements
with the appropriate CICS statements.
MODIFY MAP is replaced with a move
for the DFLD to build the screen buffer.
Cursor positioning is translated.
Maps are displayed with EXEC CICS SEND
and received with EXEC CICS RECEIVE.
And what about navigation and ADS/A security…
Navigation throughout the application
is maintained.
ADS/A security is built in to the migrated
application.
ADS/O statements for invoking the next
dialogue are converted to CICS XCTL’s as are ADS/A
definitions for RESPONSES and FUNCTIONS.
ADS/O LINK becomes a CICS CALL.
Program to program communication is
maintained.
And special ADS/O functions …
ADS/O functions are replaced with the
appropriate CICS or COBOL statements.
SUBSTRING is converted to FIELD POSTIONING.
The DO verb is replaced with inline
code and DO WHILE structures are replaced with PERFORM
UNTIL structures.
INIT becomes INITIALIZE.
All information obtainable via
CALL ADSOINFO is available to the converted application.
Back
to Top
Home
- Solutions
- Company History
- Consulting
Services
FAQ - Our
Clients - Customer
Support -
|
|
