BankDemo consists of 5 VSAM files. Each file has its own significance and accessed either by a single or multiple screens. Data from these files were downloaded from the mainframe and saved in a temporary folder at C:\Workshop\zOS-Data (flat files format).
Run the following command to copy data files from a temporary folder to an Enterprise Server data directory. We do this in order to dump data onto a VSAM files and eventually to an Aurora DB.
copy C:\Workshop\zOS-Data\*.PS.dat C:\ES-LAB\Data
Run the following command to submit BNKDVSAM.jcl. This JCL allocates VSAM KSDS files in the Enterprise Server and copies flat files data into the new VSAM KSDS files.
cassub -jC:\Workshop\zOS-Application\JCL\BNKDVSAM.jcl -rESLAB
Run the following command to navigate to the folder where catalog file is located.
Scan the catalog file by invoking following command. This command scans catalog and creates listing (R_2.dat), configuration files (static.cfg) which will be used in the following step.
mfdbcatc -s -c C:\ES-LAB\Catalog\CATALOG.DAT
Run the following command to update catalog file by replacing physical VSAM file locations with aurora database url.
mfdbcatc -u -c C:\ES-LAB\Catalog\CATALOG.DAT -fs C:\ES-LAB\Data -h aurora-mf-lab-db -d vsam -v
Run the following commands to swap catalog files to make new catalog file as an active.
ren CATALOG.DAT CATALOG.DAT.old ren NEWCATALOG.DAT CATALOG.DAT
Open the folder, C:\ES-LAB\Catalog and make sure the files were re-named successfully.
Start ESLAB server using following command.
Please be patient!!! The ESLAB is going to take couple of minutes to start. Run following steps once the above highlighted message was displayed.
Run the following command to upload data files into Aurora database using the commands generated by mfdbcatc utility (step 11 & 12). These commands were stored in the file named deployfile.