Internal document on how to run the port:

contemplated:
2nd phase - move to sqlite; all info -> external tables
3rd phase - transformations -> configuration files

'pcre_free' causes ABEND on 'USER COMPLETION CODE=4083 REASON CODE=00000003'. 
I did not have this problem when running in C.  This issue needs more
investigation.

installation:
---------------
<- load the cobol
<- compile the cobol
<- how to integrate to 'system' -> <pcre.h>
http://www-01.ibm.com/support/docview.wss?uid=swg27003846&aid=1

>>>>>>>>>>>>>>>>>>>>

I have not yet tested pcregrep.c, or any other module that is outside the core
PCRE functionality and will not turn my attention to those before the core
functionality is tested and COBOL/PLI API is developed and tested.  I assume
that I will need some more minimal changes as we go.

<<<<<<<<<<<<<<<<<<<<

On windows
----------

follow documentation
--------------------
pcre.h.generic -> pcre.h in port work directory
config.h.generic -> config.h in port work directory

include.cmd
-----------
change 'set INLIB=pcre-8.31' appropriately
see if there are new libraries or extensions to ignore
Run include.cmd
components:
include.cmd
include.pl
generates:
include.txt 

dictionary.cmd
--------------
change 'set INLIB=pcre-8.31' appropriately
run dictionary.cmd
Note (for future automation) new entries are printed.)  
rename dictionary.txt and newdictionary.txt so newdictionary will be in
  effect
components:
dictionary.cmd
dictionary.pl
dictionary.txt -> other processes -> mainframe
internal information:
config.h, pcre.h, pcre_chartable.c are marked to be taken from the port
  work directory
generates:
newdictionary.txt to replace dictionary.txt
Note: make sure that config.h, pcre.h, cobapi.c, pcrzfunc.c, pcre_chartables.c
  are in 'pcreport' directory (logically and phisically)<=== might be an issue!

twick names
-----------
This is the time to twick names
new and twicked names should reflect in the compile list for build JCL or 
mark  as 'N'/'U' in change column (i.e. do not process).
Also, new components of 'C' type need to be added to indicate copy only
compilelist.txt that is used to store/document all that need or need not
compile
  
autoconv.cmd
------------
run autoconv.cmd
components:
autoconv.cmd
autoconv.pl
dictionary.txt
generates:
zos.load.txt -> mainframe (includes the aforementioned port work
  dircrtory components)
relate.txt

buildjcl.cmd
------------
components:
buildjcl.pl
dictionary.txt
JCLtemplate.txt
compilelist.txt <- 'needcomplie.txt' is the master list for that
lkedxref.txt 
generates:
compile.jcl 
compile.jcl + JCLREADY.txt-> zos.jcl.txt -> mainframe


<- DEMOD for LKED is not created
<- in the long run, add HLQ.PCRE.HEADER library and copy all headers there as
   well for such concatenation.  Establish header list automatically.
   Installation should be modified to reflect long term header incorporation.
<- Also, manually, change ./ ADD to ./ REPL in zos.jcl.txt but on MF side.
<- Establish the ADDJCL.JCL IEBUPDTE job in the installation package for initial
   IEBUPDTE.
<- Also, I need a job to load lked and replace jcl

Comment:
this should run twice, first time with empty lkedxref.txt {only headline:
  TYPE,MEMBER,TOKEN}, then run on mainframe and import the SYSOUT.
Now do:

Install on mainframe and compile.  It will fail on linkage.  Download sysout.

lkedxref.pl
-----------
components:
<- Crude '.cmd' exists [correct that]
input SYSOUT that was downloaded before
generates:
lkedxref.txt <- spits out file using redirection [correct that]
<- important: I did not run lkedxref after adding the pcobapi.c

Now run buildjcl.cmd again, with the produced lkedxref.txt
[Note that I arranged them by hand and did not automate the order]

creinclude.cmd
--------------
components:
lkedxref.txt <- referred internaly [correct that]
generates:
zos.lked.txt <- spits out file with redirection [correct that]
<- needs to generate API list...
<- the program should also insert 'N' rows for all discovered API entries to
   dictionary.txt
   
copytest.cmd
------------
copy test files <- testlist -> zos.test.txt
<- writeup

on z/OS
-------
See installation document

