Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix wrong "set extension" argument in README command line examples #174

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix wrong "set extension" argument in README command line examples #174

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -327,15 +327,15 @@ Create an empty database or a schema, make sure you can access it with a given u

Make sure that the preprocessor (gixpp) is in your path, then preprocess the COBOL source file:

gixpp -e -S -I. -ext ".,*.cpy,*.CPY" -i TEST001.cbl -o TEST001.cbsql
gixsql TEST001.cbl TEST001.cbsql -S -I. -ext ".,*.cpy,*.CPY"
gixpp -e -S -I. -E ".,*.cpy,*.CPY" -i TEST001.cbl -o TEST001.cbsql
gixsql TEST001.cbl TEST001.cbsql -S -I. -E ".,*.cpy,*.CPY"

where:

- `-e `: preprocess for ESQL (mandatory for preprocessing)
- `-S`: use static calls when emitting GixSQL library calls (this is the mode to be normally used)
- `-I.`: use the current directory for included COPY files (SQLCA is included from GixSQL's own directory)
- `-ext ".,.cpy,.CPY"`: search for COPY files with one of these extensions (comma-separated list)
- `-E ".,.cpy,.CPY"`: search for COPY files with one of these extensions (comma-separated list)
- `-i` and `-o`: input and output file paths

Another interesting option is `--picx-as`: this indicates how standard `PIC(X)` fields should be treated when sent to the DBMS. There are three possible options:
Expand Down