Kbase 11056: PORTING THE PROGRESS DEMO DATABASE
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
PORTING THE PROGRESS DEMO DATABASE
INTRODUCTION:
=============
A brief overview of the steps for porting the PROGRESS demo database
from an MS-Windows client to the AS/400 using PC Support.
WHY YOU NEED TO KNOW THIS:
===========================
The Technical Support Knowledgebase entry demonstrates how to access
the PROGRESS/400 demo database from an MS-Windows client machine.
PROCEDURAL APPROACH:
====================
1) Create the required environment on the AS/400.
A) CRTLIB - Create library on the AS/400.
Library - The name of the library.
Library Type - Defines the type of library.
Text Description - Defines the contents of the library.
B) CRTDTADCT - Create AS/400 Data Dictionary.
Data dictionary - The name of the data dictionary.
Text description - Defines the contents of the data dictionary.
C) PROUPDPXD - Create Progress extended data dictionary.
Dictionary library - The name of the AS/400 library that
contains the native (AS/400)
dictionary that you want to port
to a PROGRESS database.
D) CRTPF - Create AS/400 physical file
(physical files can contain data or
program source code).
File - The name of the AS/400 physical file
you want to creat.
Library - The name of the library where you want to create
the physical file.
Record length - the size of the maximum record length of the
PROGRESS database files, or the size of the
longest character string of your PROGRESS
data definition file.
2) Create the neccessary PROGRESS data definitions and data files.
A) PROLODDFN - Load file definitions into the
extended data dictionary.
Dictionary Library - The name of the extended
Dictionary you created
to hold the PROGRESS database.
From File - The name of the physical file that
contains the PROGRESS data
definition file.
Library - The name of the library where the
physical file resides.
From member - The name of FROMFILE member.
To library - Enter a library name.
B) PROLODDTA - Load data to the library/file.
Dictionary library - The name of the extended dictionary.
From file - The name of the physical file
containing the PROGRESS data.
Library - The name of the library where the
FROMFILE resides.
To File - The name of the physical file you are
loading (from PROLODDFN).
Library - The name of the library where the
TOFILE resides.
From member - The name of the member containing the
PROGRESS data.
To member - The name of the member where you want
to load the FROMMBR data.
(Note: There can be only one member per physical file.
It is created by PROLODDFN and it has the same name
as the physical file).
3) Create the PROGRESS/400 data definition file and transfer the
file to the PC.
A) PRODMPDFN - Dump definitions of all the files into
files into the extended data dictionary
and creates the specified file.
Dictionary library - The name of the extended dictionary.
To file - The name of the file where you want
PRODMPDFN to put the dumped
definitions. (file created by
PRODMPDFN).
Library - The name of the library where the
TOFILE resides or will reside.
From file - Enter *ALL to dump all the data
definitions or the name of the single
file. (*ALL is required when creating
the schema holder database.
NOTE: there is currently a bug when
selecting only one file for updates.
Therefore, for UPDATES - you must
select *ALL).
From member - The name of the member when
FROMFILE is not *ALL.
From library - The FROMFILE library.
To member - The name of the NEW member where
PRODMPDFN will place the existing
data definition file.
To file format length - The TOFILE record length.
Include AS/400 - *YES (if you enter *NO, the AS/400
DB information data definitions are not added to
file and you cannot use the file
to create a schema holder database for
an AS/400 file).
B) Use transfer protocol utilities (such as PC Support) to
transfer the the dumped data definitions and data files.
For more information reference your transfer utility's
documentation.
4) Create a schema holder database on the client machine
and load the PROGRESS/400 data definitions file to the
schema holder database.
A) PRODB demo empty.
B) Use the PROGRESS Dictionary to load AS/400 .df and .d files.
ON LINE PROCEDURES OR UTILITIES:
===============================
Progress Dictionary: AS/400 dump and load utilities.
Progress Utility : PRODB to create an empty schema holder database.
REFERENCES TO WRITTEN DOCUMENTATION:
====================================
See Chapter 4 "Porting to Other PROGRESS Platforms", of the
PROGRESS/400 Server Guide.
Progress Software Technical Support Note # 11056